Mobile initiated only mode

ABSTRACT

A wireless device in an RRC connected state receives a radio resource control (RRC) message from a base station. The wireless device transitions from the RRC connected state to an RRC inactive station in response to the RRC message. The RRC message indicates an active time period in which the wireless device is reachable by paging. The wireless device monitors to receive a paging message during the active time period after the transitioning. The wireless device activates a mobile initiated communication only (MICO) mode in response to an expiration of the active time period. The wireless stops monitoring for the paging message in response to the expiration of the active time period.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 62/804,066, filed Feb. 11, 2019, which is hereby incorporated by reference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present invention are described herein with reference to the drawings.

FIG. 1 is a diagram of an example 5G system architecture as per an aspect of an embodiment of the present disclosure.

FIG. 2 is a diagram of an example 5G System architecture as per an aspect of an embodiment of the present disclosure.

FIG. 3 is a system diagram of an example wireless device and a network node in a 5G system as per an aspect of an embodiment of the present disclosure.

FIG. 4 is a system diagram of an example wireless device as per an aspect of an embodiment of the present disclosure.

FIG. 5A and FIG. 5B depict two registration management state models in UE 100 and AMF 155 as per an aspect of embodiments of the present disclosure.

FIG. 6A and FIG. 6B depict two connection management state models in UE 100 and AMF 155 as per an aspect of embodiments of the present disclosure.

FIG. 7 is diagram for classification and marking traffic as per an aspect of an embodiment of the present disclosure.

FIG. 8 is an example call flow as per an aspect of an embodiment of the present disclosure.

FIG. 9 is an example call flow as per an aspect of an embodiment of the present disclosure.

FIG. 10 is an example call flow as per an aspect of an embodiment of the present disclosure.

FIG. 11 is an example call flow as per an aspect of an embodiment of the present disclosure.

FIG. 12 is an example call flow as per an aspect of an embodiment of the present disclosure.

FIG. 13 is an example call flow as per an aspect of an embodiment of the present disclosure.

FIG. 14 is an example radio resource control (RRC) state transition aspect as per an aspect of an embodiment of the present disclosure.

FIG. 15 is an example call flow for RRC state transaction as per an aspect of an embodiment of the present disclosure.

FIG. 16 is an example call flows of RRC state transition report of a wireless device.

FIG. 17 is an example call flows of a MICO mode negotiation, activation and deactivation.

FIG. 18 is an example call flows of the MICO mode re-negotiation.

FIG. 19 is an example call flows of the MICO mode operation with active time value.

FIG. 20 illustrates an example embodiment of a present disclosure.

FIG. 21 illustrates an example embodiment of a present disclosure.

FIG. 22 illustrates an example embodiment of a present disclosure.

FIG. 23 illustrates an example flow chart from a wireless device for the present disclosure.

FIG. 24 illustrates an example flow chart from a wireless device for the present disclosure.

FIG. 25 illustrates an example flow chart from an access and mobility management function for the present disclosure.

FIG. 26 illustrates an example flow chart from a wireless device for the present disclosure.

FIG. 27 illustrates an example flow chart from a wireless device for the present disclosure.

FIG. 28 illustrates an example flow chart from a wireless device for the present disclosure.

FIG. 29 illustrates an example flow chart from a wireless device for the present disclosure.

DETAILED DESCRIPTION OF EXAMPLES

Example embodiments of the present invention enable implementation of enhanced features and functionalities in 4G/5G systems. Embodiments of the technology disclosed herein may be employed in the technical field of 4G/5G systems and network slicing for communication systems. More particularly, the embodiments of the technology disclosed herein may relate to 5G core network and 5G systems for network slicing in communication systems. Throughout the present disclosure, UE, wireless device, and mobile device are used interchangeably.

The following acronyms are used throughout the present disclosure:

5G 5th generation mobile networks

5GC 5G Core Network

5GS 5G System

5G-AN 5G Access Network

5QI 5G QoS Indicator

ACK Acknowledgement

AF Application Function

AMF Access and Mobility Management Function

AN Access Network

CDR Charging Data Record

CCNF Common Control Network Functions

CIoT Cellular IoT

CN Core Network

CP Control Plane

DDN Downlink Data Notification

DL Downlink

DN Data Network

DNN Data Network Name

DRX Discontinuous Reception

F-TEID Fully Qualified TEID

gNB next generation Node B

GPSI Generic Public Subscription Identifier

GTP GPRS Tunneling Protocol

GUTI Globally Unique Temporary Identifier

HPLMN Home Public Land Mobile Network

IMSI International Mobile Subscriber Identity

LADN Local Area Data Network

LI Lawful Intercept

MEI Mobile Equipment Identifier

MICO Mobile Initiated Connection Only

MME Mobility Management Entity

MO Mobile Originated

MSISDN Mobile Subscriber ISDN

MT Mobile Terminating

N3IWF Non-3GPP InterWorking Function

NAI Network Access Identifier

NAS Non-Access Stratum

NB-IoT Narrow Band IoT

NEF Network Exposure Function

NF Network Function

NGAP Next Generation Application Protocol

NR New Radio

NRF Network Repository Function

NSI Network Slice Instance

NSSAI Network Slice Selection Assistance Information

NSSF Network Slice Selection Function

OCS Online Charging System

OFCS Offline Charging System

PCF Policy Control Function

PDU Packet/Protocol Data Unit

PEI Permanent Equipment Identifier

PLMN Public Land Mobile Network

PRACH Physical Random Access CHannel

PLMN Public Land Mobile Network

RAN Radio Access Network

QFI QoS Flow Identity

RM Registration Management

S1-AP S1 Application Protocol

SBA Service Based Architecture

SEA Security Anchor Function

SCM Security Context Management

SI System Information

SIB System Information Block

SMF Session Management Function

SMSF SMS Function

S-NSSAI Single Network Slice Selection Assistance information

SUCI Served User Correlation ID

SUPI Subscriber Permanent Identifier

TEID Tunnel Endpoint Identifier

UE User Equipment

UL Uplink

UL CL Uplink Classifier

UPF User Plane Function

VPLMN Visited Public Land Mobile Network

Example FIG. 1 and FIG. 2 depict a 5G system comprising of access networks and 5G core network. An example 5G access network may comprise an access network connecting to a 5G core network. An access network may comprise an NG-RAN 105 and/or non-3GPP AN 165. An example 5G core network may connect to one or more 5G access networks 5G-AN and/or NG-RANs. 5G core network may comprise functional elements or network functions as in example FIG. 1 and example FIG. 2 where interfaces may be employed for communication among the functional elements and/or network elements.

In an example, a network function may be a processing function in a network, which may have a functional behavior and/or interfaces. A network function may be implemented either as a network element on a dedicated hardware, and/or a network node as depicted in FIG. 3 and FIG. 4, or as a software instance running on a dedicated hardware and/or shared hardware, or as a virtualized function instantiated on an appropriate platform.

In an example, access and mobility management function, AMF 155, may include the following functionalities (some of the AMF 155 functionalities may be supported in a single instance of an AMF 155): termination of RAN 105 CP interface (N2), termination of NAS (N1), NAS ciphering and integrity protection, registration management, connection management, reachability management, mobility management, lawful intercept (for AMF 155 events and interface to LI system), provide transport for session management, SM messages between UE 100 and SMF 160, transparent proxy for routing SM messages, access authentication, access authorization, provide transport for SMS messages between UE 100 and SMSF, security anchor function, SEA, interaction with the AUSF 150 and the UE 100, receiving the intermediate key established as a result of the UE 100 authentication process, security context management, SCM, that receives a key from the SEA that it uses to derive access network specific keys, and/or the like.

In an example, the AMF 155 may support non-3GPP access networks through N2 interface with N3IWF 170, NAS signaling with a UE 100 over N3IWF 170, authentication of UEs connected over N3IWF 170, management of mobility, authentication, and separate security context state(s) of a UE 100 connected via non-3GPP access 165 or connected via 3GPP access 105 and non-3GPP access 165 simultaneously, support of a coordinated RM context valid over 3GPP access 105 and non 3GPP access 165, support of CM management contexts for the UE 100 for connectivity over non-3GPP access, and/or the like.

In an example, an AMF 155 region may comprise one or multiple AMF 155 sets. The AMF 155 set may comprise some AMF 155 that serve a given area and/or network slice(s). In an example, multiple AMF 155 sets may be per AMF 155 region and/or network slice(s). Application identifier may be an identifier that may be mapped to a specific application traffic detection rule. Configured NSSAI may be an NSSAI that may be provisioned in a UE 100. DN 115 access identifier (DNAI), for a DNN, may be an identifier of a user plane access to a DN 115. Initial registration may be related to a UE 100 registration in RM-DEREGISTERED 500, 520 states. N2AP UE 100 association may be a logical per UE 100 association between a 5G AN node and an AMF 155. N2AP UE-TNLA-binding may be a binding between a N2AP UE 100 association and a specific transport network layer, TNL association for a given UE 100.

In an example, session management function, SMF 160, may include one or more of the following functionalities (one or more of the SMF 160 functionalities may be supported in a single instance of a SMF 160): session management (e.g. session establishment, modify and release, including tunnel maintain between UPF 110 and AN 105 node), UE 100 IP address allocation & management (including optional authorization), selection and control of UP function(s), configuration of traffic steering at UPF 110 to route traffic to proper destination, termination of interfaces towards policy control functions, control part of policy enforcement and QoS. lawful intercept (for SM events and interface to LI System), termination of SM parts of NAS messages, downlink data notification, initiation of AN specific SM information, sent via AMF 155 over N2 to (R)AN 105, determination of SSC mode of a session, roaming functionality, handling local enforcement to apply QoS SLAs (VPLMN), charging data collection and charging interface (VPLMN), lawful intercept (in VPLMN for SM events and interface to LI System), support for interaction with external DN 115 for transport of signaling for PDU session authorization/authentication by external DN 115, and/or the like.

In an example, a user plane function, UPF 110, may include one or more of the following functionalities (some of the UPF 110 functionalities may be supported in a single instance of a UPF 110): anchor point for Intra-/Inter-RAT mobility (when applicable), external PDU session point of interconnect to DN 115, packet routing & forwarding, packet inspection and user plane part of policy rule enforcement, lawful intercept (UP collection), traffic usage reporting, uplink classifier to support routing traffic flows to a data network, branching point to support multi-homed PDU session(s), QoS handling for user plane, uplink traffic verification (SDF to QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering, downlink data notification triggering, and/or the like.

In an example, the UE 100 IP address management may include allocation and release of the UE 100 IP address and/or renewal of the allocated IP address. The UE 100 may set a requested PDU type during a PDU session establishment procedure based on its IP stack capabilities and/or configuration. In an example, the SMF 160 may select PDU type of a PDU session. In an example, if the SMF 160 receives a request with PDU type set to IP, the SMF 160 may select PDU type IPv4 or IPv6 based on DNN configuration and/or operator policies. In an example, the SMF 160 may provide a cause value to the UE 100 to indicate whether the other IP version is supported on the DNN. In an example, if the SMF 160 receives a request for PDU type IPv4 or IPv6 and the requested IP version is supported by the DNN the SMF 160 may select the requested PDU type.

In an example embodiment, the 5GC elements and UE 100 may support the following mechanisms: during a PDU session establishment procedure, the SMF 160 may send the IP address to the UE 100 via SM NAS signaling. The IPv4 address allocation and/or IPv4 parameter configuration via DHCPv4 may be employed once PDU session may be established. IPv6 prefix allocation may be supported via IPv6 stateless autoconfiguration, if IPv6 is supported. In an example, 5GC network elements may support IPv6 parameter configuration via stateless DHCPv6.

The 5GC may support the allocation of a static IPv4 address and/or a static IPv6 prefix based on subscription information in a UDM 140 and/or based on the configuration on a per-subscriber, per-DNN basis.

User plane function(s) (UPF 110) may handle the user plane path of PDU sessions. A UPF 110 that provides the interface to a data network may support functionality of a PDU session anchor.

In an example, a policy control function, PCF 135, may support unified policy framework to govern network behavior, provide policy rules to control plane function(s) to enforce policy rules, implement a front end to access subscription information relevant for policy decisions in a user data repository (UDR), and/or the like.

A network exposure function, NEF 125, may provide means to securely expose the services and capabilities provided by the 3GPP network functions, translate between information exchanged with the AF 145 and information exchanged with the internal network functions, receive information from other network functions, and/or the like.

In an example, an network repository function, NRF 130 may support service discovery function that may receive NF discovery request from NF instance, provide information about the discovered NF instances (be discovered) to the NF instance, and maintain information about available NF instances and their supported services, and/or the like.

In an example, an NSSF 120 may select a set of network slice instances serving the UE 100, may determine allowed NSSAI. In an example, the NSSF 120 may determine the AMF 155 set to be employed to serve the UE 100, and/or, based on configuration, determine a list of candidate AMF 155(s) 155 by querying the NRF 130.

In an example, stored data in a UDR may include at least user subscription data, including at least subscription identifiers, security credentials, access and mobility related subscription data, session related subscription data, policy data, and/or the like.

In an example, an AUSF 150 may support authentication server function (AUSF 150).

In an example, an application function (AF), AF 145, may interact with the 3GPP core network to provide services. In an example, based on operator deployment, application functions may be trusted by the operator to interact directly with relevant network functions. Application functions not allowed by the operator to access directly the network functions may use an external exposure framework (e.g., via the NEF 125) to interact with relevant network functions.

In an example, control plane interface between the (R)AN 105 and the 5G core may support connection of multiple different kinds of AN(s) (e.g. 3GPP RAN 105, N3IWF 170 for Un-trusted access 165) to the 5GC via a control plane protocol. In an example, an N2 AP protocol may be employed for both the 3GPP access 105 and non-3GPP access 165. In an example, control plane interface between the (R)AN 105 and the 5G core may support decoupling between AMF 155 and other functions such as SMF 160 that may need to control the services supported by AN(s) (e.g. control of the UP resources in the AN 105 for a PDU session).

In an example, the 5GC may provide policy information from the PCF 135 to the UE 100. In an example, the policy information may comprise: access network discovery and selection policy, UE 100 route selection policy (URSP), SSC mode selection policy (SSCMSP), network slice selection policy (NSSP), DNN selection policy, non-seamless offload policy, and/or the like.

In an example, as depicted in example FIG. 5A and FIG. 5B, the registration management, RM may be employed to register or de-register a UE/user 100 with the network and establish the user context in the network. Connection management may be employed to establish and release the signaling connection between the UE 100 and the AMF 155.

In an example, a UE 100 may register with the network to receive services that require registration. In an example, the UE 100 may update its registration with the network periodically in order to remain reachable (periodic registration update), or upon mobility (e.g., mobility registration update), or to update its capabilities or to re-negotiate protocol parameters.

In an example, an initial registration procedure as depicted in example FIG. 8 and FIG. 9 may involve execution of network access control functions (e.g. user authentication and access authorization based on subscription profiles in UDM 140). Example FIG. 9 is a continuation of the initial registration procedure depicted in FIG. 8. As a result of the initial registration procedure, the identity of the serving AMF 155 may be registered in a UDM 140.

In an example, the registration management, RM procedures may be applicable over both 3GPP access 105 and non 3GPP access 165.

An example FIG. 5A may depict the RM states of a UE 100 as observed by the UE 100 and AMF 155. In an example embodiment, two RM states may be employed in the UE 100 and the AMF 155 that may reflect the registration status of the UE 100 in the selected PLMN: RM-DEREGISTERED 500, and RM-REGISTERED 510. In an example, in the RM DEREGISTERED state 500, the UE 100 may not be registered with the network. The UE 100 context in the AMF 155 may not hold valid location or routing information for the UE 100 so the UE 100 may not be reachable by the AMF 155. In an example, the UE 100 context may be stored in the UE 100 and the AMF 155. In an example, in the RM REGISTERED state 510, the UE 100 may be registered with the network. In the RM-REGISTERED 510 state, the UE 100 may receive services that may require registration with the network.

In an example embodiment, two RM states may be employed in AMF 155 for the UE 100 that may reflect the registration status of the UE 100 in the selected PLMN: RM-DEREGISTERED 520, and RM-REGISTERED 530.

As depicted in example FIG. 6A and FIG. 6B, connection management, CM, may comprise establishing and releasing a signaling connection between a UE 100 and an AMF 155 over N1 interface. The signaling connection may be employed to enable NAS signaling exchange between the UE 100 and the core network. The signaling connection between the UE 100 and the AMF 155 may comprise both the AN signaling connection between the UE 100 and the (R)AN 105 (e.g. RRC connection over 3GPP access) and the N2 connection for the UE 100 between the AN and the AMF 155.

As depicted in example FIG. 6A and FIG. 6B, two CM states may be employed for the NAS signaling connectivity of the UE 100 with the AMF 155, CM-IDLE 600, 620 and CM-CONNECTED 610, 630. A UE 100 in CM-IDLE 600 state may be in RM-REGISTERED 510 state and may have no NAS signaling connection established with the AMF 155 over N1. The UE 100 may perform cell selection, cell reselection, PLMN selection, and/or the like. A UE 100 in CM-CONNECTED 610 state may have a NAS signaling connection with the AMF 155 over N1.

In an example embodiment two CM states may be employed for the UE 100 at the AMF 155, CM-IDLE 620 and CM-CONNECTED 630.

In an example, an RRC inactive state may apply to NG-RAN (e.g. it may apply to NR and E-UTRA connected to 5G CN). The AMF 155, based on network configuration, may provide assistance information to the NG RAN 105, to assist the NG RAN's 105 decision whether the UE 100 may be sent to RRC inactive state. When a UE 100 is CM-CONNECTED 610 with RRC inactive state, the UE 100 may resume the RRC connection due to uplink data pending, mobile initiated signaling procedure, as a response to RAN 105 paging, to notify the network that it has left the RAN 105 notification area, and/or the like.

In an example, a NAS signaling connection management may include establishing and releasing a NAS signaling connection. A NAS signaling connection establishment function may be provided by the UE 100 and the AMF 155 to establish the NAS signaling connection for the UE 100 in CM-IDLE 600 state. The procedure of releasing the NAS signaling connection may be initiated by the 5G (R)AN 105 node or the AMF 155.

In an example, reachability management of a UE 100 may detect whether the UE 100 is reachable and may provide the UE 100 location (e.g. access node) to the network to reach the UE 100. Reachability management may be done by paging the UE 100 and the UE 100 location tracking. The UE 100 location tracking may include both UE 100 registration area tracking and UE 100 reachability tracking. The UE 100 and the AMF 155 may negotiate UE 100 reachability characteristics in CM-IDLE 600, 620 state during registration and registration update procedures.

In an example, two UE 100 reachability categories may be negotiated between a UE 100 and an AMF 155 for CM-IDLE 600, 620 state. 1) UE 100 reachability allowing mobile device terminated data while the UE 100 is CM-IDLE 600 mode. 2) Mobile initiated connection only (MICO) mode. The 5GC may support a PDU connectivity service that provides exchange of PDUs between the UE 100 and a data network identified by a DNN. The PDU connectivity service may be supported via PDU sessions that are established upon request from the UE 100.

In an example, a PDU session may support one or more PDU session types. PDU sessions may be established (e.g. upon UE 100 request), modified (e.g. upon UE 100 and 5GC request) and/or released (e.g. upon UE 100 and 5GC request) using NAS SM signaling exchanged over N1 between the UE 100 and the SMF 160. Upon request from an application server, the 5GC may be able to trigger a specific application in the UE 100. When receiving the trigger, the UE 100 may send it to the identified application in the UE 100. The identified application in the UE 100 may establish a PDU session to a specific DNN.

In an example, the 5G QoS model may support a QoS flow based framework as depicted in example FIG. 7. The 5G QoS model may support both QoS flows that require a guaranteed flow bit rate and QoS flows that may not require a guaranteed flow bit rate. In an example, the 5G QoS model may support reflective QoS. The QoS model may comprise flow mapping or packet marking at the UPF 110 (CN_UP) 110, AN 105 and/or the UE 100. In an example, packets may arrive from and/or destined to the application/service layer 730 of UE 100, UPF 110 (CN_UP) 110, and/or the AF 145.

In an example, the QoS flow may be a granularity of QoS differentiation in a PDU session. A QoS flow ID, QFI, may be employed to identify the QoS flow in the 5G system. In an example, user plane traffic with the same QFI within a PDU session may receive the same traffic forwarding treatment. The QFI may be carried in an encapsulation header on N3 and/or N9 (e.g. without any changes to the end-to-end packet header). In an example, the QFI may be applied to PDUs with different types of payload. The QFI may be unique within a PDU session.

In an example, the QoS parameters of a QoS flow may be provided to the (R)AN 105 as a QoS profile over N2 at PDU session establishment, QoS flow establishment, or when NG-RAN is used at every time the user plane is activated. In an example, a default QoS rule may be required for every PDU session. The SMF 160 may allocate the QFI for a QoS flow and may derive QoS parameters from the information provided by the PCF 135. In an example, the SMF 160 may provide the QFI together with the QoS profile containing the QoS parameters of a QoS flow to the (R)AN 105.

In an example, 5G QoS flow may be a granularity for QoS forwarding treatment in the 5G system. Traffic mapped to the same 5G QoS flow may receive the same forwarding treatment (e.g. scheduling policy, queue management policy, rate shaping policy, RLC configuration, and/or the like). In an example, providing different QoS forwarding treatment may require separate 5G QoS flows.

In an example, a 5G QoS indicator may be a scalar that may be employed as a reference to a specific QoS forwarding behavior (e.g. packet loss rate, packet delay budget) to be provided to a 5G QoS flow. In an example, the 5G QoS indicator may be implemented in the access network by the 5QI referencing node specific parameters that may control the QoS forwarding treatment (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, and/or the like).

In an example, 5GC may support edge computing and may enable operator(s) and 3rd party services to be hosted close to the UE's access point of attachment. The 5G core network may select a UPF 110 close to the UE 100 and may execute the traffic steering from the UPF 110 to the local data network via a N6 interface. In an example, the selection and traffic steering may be based on the UE's 100 subscription data, UE 100 location, the information from application function AF 145, policy, other related traffic rules, and/or the like. In an example, the 5G core network may expose network information and capabilities to an edge computing application function. The functionality support for edge computing may include local routing where the 5G core network may select a UPF 110 to route the user traffic to the local data network, traffic steering where the 5G core network may select the traffic to be routed to the applications in the local data network, session and service continuity to enable UE 100 and application mobility, user plane selection and reselection, e.g. based on input from application function, network capability exposure where 5G core network and application function may provide information to each other via NEf 125, QoS and charging where PCF 135 may provide rules for QoS control and charging for the traffic routed to the local data network, support of local area data network where 5G core network may provide support to connect to the LADN in a certain area where the applications are deployed, and/or the like.

An example 5G system may be a 3GPP system comprising of 5G access network 105, 5G core network and a UE 100, and/or the like. Allowed NSSAI may be an NSSAI provided by a serving PLMN during e.g. a registration procedure, indicating the NSSAI allowed by the network for the UE 100 in the serving PLMN for the current registration area.

In an example, a PDU connectivity service may provide exchange of PDUs between a UE 100 and a data network. A PDU session may be an association between the UE 100 and the data network, DN 115, that may provide the PDU connectivity service. The type of association may be IP, Ethernet and/or unstructured.

Establishment of user plane connectivity to a data network via network slice instance(s) may comprise the following: performing a RM procedure to select an AMF 155 that supports the required network slices, and establishing one or more PDU session(s) to the required data network via the network slice instance(s).

In an example, the set of network slices for a UE 100 may be changed at any time while the UE 100 may be registered with the network, and may be initiated by the network, or the UE 100.

In an example, a periodic registration update may be UE 100 re-registration at expiry of a periodic registration timer. A requested NSSAI may be a NSSAI that the UE 100 may provide to the network.

In an example, a service based interface may represent how a set of services may be provided/exposed by a given NF.

In an example, a service continuity may be an uninterrupted user experience of a service, including the cases where the IP address and/or anchoring point may change. In an example, a session continuity may refer to continuity of a PDU session. For PDU session of IP type session continuity may imply that the IP address is preserved for the lifetime of the PDU session. An uplink classifier may be a UPF 110 functionality that aims at diverting uplink traffic, based on filter rules provided by the SMF 160, towards data network, DN 115.

In an example, the 5G system architecture may support data connectivity and services enabling deployments to use techniques such as e.g. network function virtualization and/or software defined networking. The 5G system architecture may leverage service-based interactions between control plane (CP) network functions where identified. In 5G system architecture, separation of the user plane (UP) functions from the control plane functions may be considered. A 5G system may enable a network function to interact with other NF(s) directly if required.

In an example, the 5G system may reduce dependencies between the access network (AN) and the core network (CN). The architecture may comprise a converged access-agnostic core network with a common AN-CN interface which may integrate different 3GPP and non-3GPP access types.

In an example, the 5G system may support a unified authentication framework, stateless NFs, where the compute resource is decoupled from the storage resource, capability exposure, and concurrent access to local and centralized services. To support low latency services and access to local data networks, UP functions may be deployed close to the access network.

In an example, the 5G system may support roaming with home routed traffic and/or local breakout traffic in the visited PLMN. An example 5G architecture may be service-based and the interaction between network functions may be represented in two ways. (1) As service-based representation (depicted in example FIG. 1), where network functions within the control plane, may enable other authorized network functions to access their services. This representation may also include point-to-point reference points where necessary. (2) Reference point representation, showing the interaction between the NF services in the network functions described by point-to-point reference point (e.g. N11) between any two network functions.

In an example, a network slice may comprise the core network control plane and user plane network functions, the 5G Radio Access Network; the N3IWF functions to the non-3GPP Access Network, and/or the like. Network slices may differ for supported features and network function implementation. The operator may deploy multiple network slice instances delivering the same features but for different groups of UEs, e.g. as they deliver a different committed service and/or because they may be dedicated to a customer. The NSSF 120 may store the mapping information between slice instance ID and NF ID (or NF address).

In an example, a UE 100 may simultaneously be served by one or more network slice instances via a 5G-AN. In an example, the UE 100 may be served by k network slices (e.g. k=8, 16, etc) at a time. An AMF 155 instance serving the UE 100 logically may belong to a network slice instance serving the UE 100.

In an example, a PDU session may belong to one specific network slice instance per PLMN. In an example, different network slice instances may not share a PDU session. Different slices may have slice-specific PDU sessions using the same DNN.

An S-NSSAI (Single Network Slice Selection Assistance information) may identify a network slice. An S-NSSAI may comprise a slice/service type (SST), which may refer to the expected network slice behavior in terms of features and services; and/or a slice differentiator (SD). A slice differentiator may be optional information that may complement the slice/service type(s) to allow further differentiation for selecting a network slice instance from potentially multiple network slice instances that comply with the indicated slice/service type. In an example, the same network slice instance may be selected employing different S-NSSAIs. The CN part of a network slice instance(s) serving a UE 100 may be selected by CN.

In an example, subscription data may include the S-NSSAI(s) of the network slices that the UE 100 subscribes to. One or more S-NSSAIs may be marked as default S-NSSAI. In an example, k S-NSSAI may be marked default S-NSSAI (e.g. k=8, 16, etc.). In an example, the UE 100 may subscribe to more than 8 S-NSSAIs.

In an example, a UE 100 may be configured by the HPLMN with a configured NSSAI per PLMN. Upon successful completion of a UE's registration procedure, the UE 100 may obtain from the AMF 155 an Allowed NSSAI for this PLMN, which may include one or more S-NSSAIs.

In an example, the Allowed NSSAI may take precedence over the configured NSSAI for a PLMN. The UE 100 may use the S-NSSAIs in the allowed NSSAI corresponding to a network slice for the subsequent network slice selection related procedures in the serving PLMN.

In an example, the establishment of user plane connectivity to a data network via a network slice instance(s) may comprise: performing a RM procedure to select an AMF 155 that may support the required network slices, establishing one or more PDU sessions to the required data network via the network slice instance(s), and/or the like.

In an example, when a UE 100 registers with a PLMN, if the UE 100 for the PLMN has a configured NSSAI or an allowed NSSAI, the UE 100 may provide to the network in RRC and NAS layer a requested NSSAI comprising the S-NSSAI(s) corresponding to the slice(s) to which the UE 100 attempts to register, a temporary user ID if one was assigned to the UE, and/or the like. The requested NSSAI may be configured-NSSAI, allowed-NSSAI, and/or the like.

In an example, when a UE 100 registers with a PLMN, if for the PLMN the UE 100 has no configured NSSAI or allowed NSSAI, the RAN 105 may route NAS signaling from/to the UE 100 to/from a default AMF 155.

In an example, the network, based on local policies, subscription changes and/or UE 100 mobility, may change the set of permitted network slice(s) to which the UE 100 is registered. In an example, the network may perform the change during a registration procedure or trigger a notification towards the UE 100 of the change of the supported network slices using an RM procedure (which may trigger a registration procedure). The network may provide the UE 100 with a new allowed NSSAI and tracking area list.

In an example, during a registration procedure in a PLMN, in case the network decides that the UE 100 should be served by a different AMF 155 based on network slice(s) aspects, the AMF 155 that first received the registration request may redirect the registration request to another AMF 155 via the RAN 105 or via direct signaling between the initial AMF 155 and the target AMF 155.

In an example, the network operator may provision the UE 100 with network slice selection policy (NSSP). The NSSP may comprise one or more NSSP rules.

In an example, if a UE 100 has one or more PDU sessions established corresponding to the a specific S-NSSAI, the UE 100 may route the user data of the application in one of the PDU sessions, unless other conditions in the UE 100 may prohibit the use of the PDU sessions. If the application provides a DNN, then the UE 100 may consider the DNN to determine which PDU session to use. In an example, if the UE 100 does not have a PDU session established with the specific S-NSSAI, the UE 100 may request a new PDU session corresponding to the S-NSSAI and with the DNN that may be provided by the application. In an example, in order for the RAN 105 to select a proper resource for supporting network slicing in the RAN 105, the RAN 105 may be aware of the network slices used by the UE 100.

In an example, an AMF 155 may select an SMF 160 in a network slice instance based on S-NSSAI, DNN and/or other information e.g. UE 100 subscription and local operator policies, and/or the like, when the UE 100 triggers the establishment of a PDU session. The selected SMF 160 may establish the PDU session based on S-NSSAI and DNN.

In an example, in order to support network-controlled privacy of slice information for the slices the UE 100 may access, when the UE 100 is aware or configured that privacy considerations may apply to NSSAI, the UE 100 may not include NSSAI in NAS signaling unless the UE 100 has a NAS security context and the UE 100 may not include NSSAI in unprotected RRC signaling.

In an example, for roaming scenarios, the network slice specific network functions in VPLMN and HPLMN may be selected based on the S-NSSAI provided by the UE 100 during PDU connection establishment. If a standardized S-NSSAI is used, selection of slice specific NF instances may be done by each PLMN based on the provided S-NSSAI. In an example, the VPLMN may map the S-NSSAI of HPLMN to a S-NSSAI of VPLMN based on roaming agreement (e.g., including mapping to a default S-NSSAI of VPLMN). In an example, the selection of slice specific NF instance in VPLMN may be done based on the S-NSSAI of VPLMN. In an example, the selection of any slice specific NF instance in HPLMN may be based on the S-NSSAI of HPLMN.

As depicted in example FIG. 8 and FIG. 9, a registration procedure may be performed by the UE 100 to get authorized to receive services, to enable mobility tracking, to enable reachability, and/or the like.

In an example, the UE 100 may send to the (R)AN 105 an AN message 805 (comprising AN parameters, RM-NAS registration request (registration type, SUCI or SUPI or 5G-GUTI, last visited TAI (if available), security parameters, requested NSSAI, mapping of requested NSSAI, UE 100 5GC capability, PDU session status, PDU session(s) to be re-activated, Follow on request, MICO mode preference, and/or the like), and/or the like). In an example, in case of NG-RAN, the AN parameters may include e.g. SUCI or SUPI or the 5G-GUTI, the Selected PLMN ID and requested NSSAI, and/or the like. In an example, the AN parameters may comprise establishment cause. The establishment cause may provide the reason for requesting the establishment of an RRC connection. In an example, the registration type may indicate if the UE 100 wants to perform an initial registration (e.g. the UE 100 is in RM-DEREGISTERED state), a mobility registration update (e.g., the UE 100 is in RM-REGISTERED state and initiates a registration procedure due to mobility), a periodic registration update (e.g., the UE 100 is in RM-REGISTERED state and may initiate a registration procedure due to the periodic registration update timer expiry) or an emergency registration (e.g., the UE 100 is in limited service state). In an example, if the UE 100 performing an initial registration (e.g., the UE 100 is in RM-DEREGISTERED state) to a PLMN for which the UE 100 does not already have a 5G-GUTI, the UE 100 may include its SUCI or SUPI in the registration request. The SUCI may be included if the home network has provisioned the public key to protect SUPI in the UE. If the UE 100 received a UE 100 configuration update command indicating that the UE 100 needs to re-register and the 5G-GUTI is invalid, the UE 100 may perform an initial registration and may include the SUPI in the registration request message. For an emergency registration, the SUPI may be included if the UE 100 does not have a valid 5G-GUTI available; the PEI may be included when the UE 100 has no SUPI and no valid 5G-GUTI. In other cases, the 5G-GUTI may be included and it may indicate the last serving AMF 155. If the UE 100 is already registered via a non-3GPP access in a PLMN different from the new PLMN (e.g., not the registered PLMN or an equivalent PLMN of the registered PLMN) of the 3GPP access, the UE 100 may not provide over the 3GPP access the 5G-GUTI allocated by the AMF 155 during the registration procedure over the non-3GPP access. If the UE 100 is already registered via a 3GPP access in a PLMN (e.g., the registered PLMN), different from the new PLMN (e.g. not the registered PLMN or an equivalent PLMN of the registered PLMN) of the non-3GPP access, the UE 100 may not provide over the non-3GPP access the 5G-GUTI allocated by the AMF 155 during the registration procedure over the 3GPP access. The UE 100 may provide the UE's usage setting based on its configuration. In case of initial registration or mobility registration update, the UE 100 may include the mapping of requested NSSAI, which may be the mapping of each S-NSSAI of the requested NSSAI to the S-NSSAIs of the configured NSSAI for the HPLMN, to ensure that the network is able to verify whether the S-NSSAI(s) in the requested NSSAI are permitted based on the subscribed S-NSSAIs. If available, the last visited TAI may be included in order to help the AMF 155 produce registration area for the UE. In an example, the security parameters may be used for authentication and integrity protection. requested NSSAI may indicate the network slice selection assistance information. The PDU session status may indicates the previously established PDU sessions in the UE. When the UE 100 is connected to the two AMF 155 belonging to different PLMN via 3GPP access and non-3GPP access then the PDU session status may indicate the established PDU session of the current PLMN in the UE. The PDU session(s) to be re-activated may be included to indicate the PDU session(s) for which the UE 100 may intend to activate UP connections. A PDU session corresponding to a LADN may not be included in the PDU session(s) to be re-activated when the UE 100 is outside the area of availability of the LADN. The follow on request may be included when the UE 100 may have pending uplink signaling and the UE 100 may not include PDU session(s) to be re-activated, or the registration type may indicate the UE 100 may want to perform an emergency registration.

In an example, if a SUPI is included or the 5G-GUTI does not indicate a valid AMF 155, the (R)AN 105, based on (R)AT and requested NSSAI, if available, may selects 808 an AMF 155. If UE 100 is in CM-CONNECTED state, the (R)AN 105 may forward the registration request message to the AMF 155 based on the N2 connection of the UE. If the (R)AN 105 may not select an appropriate AMF 155, it may forward the registration request to an AMF 155 which has been configured, in (R)AN 105, to perform AMF 155 selection 808.

In an example, the (R)AN 105 may send to the new AMF 155 an N2 message 810 (comprising: N2 parameters, RM-NAS registration request (registration type, SUPI or 5G-GUTI, last visited TAI (if available), security parameters, requested NSSAI, mapping of requested NSSAI, UE 100 5GC capability, PDU session status, PDU session(s) to be re-activated, follow on request, and MICO mode preference), and/or the like). In an example, when NG-RAN is used, the N2 parameters may comprise the selected PLMN ID, location information, cell identity and the RAT type related to the cell in which the UE 100 is camping. In an example, when NG-RAN is used, the N2 parameters may include the establishment cause.

In an example, the new AMF 155 may send to the old AMF 155 an Namf_Communication_UEContextTransfer (complete registration request) 815. In an example, if the UE's 5G-GUTI was included in the registration request and the serving AMF 155 has changed since last registration procedure, the new AMF 155 may invoke the Namf_Communication_UEContextTransfer service operation 815 on the old AMF 155 including the complete registration request IE, which may be integrity protected, to request the UE's SUPI and MM Context. The old AMF 155 may use the integrity protected complete registration request IE to verify if the context transfer service operation invocation corresponds to the UE 100 requested. In an example, the old AMF 155 may transfer the event subscriptions information by each NF consumer, for the UE, to the new AMF 155. In an example, if the UE 100 identifies itself with PEI, the SUPI request may be skipped.

In an example, the old AMF 155 may send to new AMF 155 a response 815 to Namf_Communication_UEContextTransfer (SUPI, MM context, SMF 160 information, PCF ID). In an example, the old AMF 155 may respond to the new AMF 155 for the Namf_Communication_UEContextTransfer invocation by including the UE's SUPI and MM context. In an example, if old AMF 155 holds information about established PDU sessions, the old AMF 155 may include SMF 160 information including S-NSSAI(s), SMF 160 identities and PDU session ID. In an example, if old AMF 155 holds information about active NGAP UE-TNLA bindings to N3IWF, the old AMF 155 may include information about the NGAP UE-TNLA bindings.

In an example, if the SUPI is not provided by the UE 100 nor retrieved from the old AMF 155 the identity request procedure 820 may be initiated by the AMF 155 sending an identity request message to the UE 100 requesting the SUCI.

In an example, the UE 100 may respond with an identity response message 820 including the SUCI. The UE 100 may derive the SUCI by using the provisioned public key of the HPLMN.

In an example, the AMF 155 may decide to initiate UE 100 authentication 825 by invoking an AUSF 150. The AMF 155 may select an AUSF 150 based on SUPI or SUCI. In an example, if the AMF 155 is configured to support emergency registration for unauthenticated SUPIs and the UE 100 indicated registration type emergency registration the AMF 155 may skip the authentication and security setup or the AMF 155 may accept that the authentication may fail and may continue the registration procedure.

In an example, the authentication 830 may be performed by Nudm_UEAuthenticate_Get operation. The AUSF 150 may discover a UDM 140. In case the AMF 155 provided a SUCI to AUSF 150, the AUSF 150 may return the SUPI to AMF 155 after the authentication is successful. In an example, if network slicing is used, the AMF 155 may decide if the registration request needs to be rerouted where the initial AMF 155 refers to the AMF 155. In an example, the AMF 155 may initiate NAS security functions. In an example, upon completion of NAS security function setup, the AMF 155 may initiate NGAP procedure to enable 5G-AN use it for securing procedures with the UE. In an example, the 5G-AN may store the security context and may acknowledge to the AMF 155. The 5G-AN may use the security context to protect the messages exchanged with the UE.

In an example, new AMF 155 may send to the old AMF 155 Namf_Communication_RegistrationCompleteNotify 835. If the AMF 155 has changed, the new AMF 155 may notify the old AMF 155 that the registration of the UE 100 in the new AMF 155 may be completed by invoking the Namf_Communication_RegistrationCompleteNotify service operation. If the authentication/security procedure fails, then the registration may be rejected, and the new AMF 155 may invoke the Namf_Communication_RegistrationCompleteNotify service operation with a reject indication reason code towards the old AMF 155. The old AMF 155 may continue as if the UE 100 context transfer service operation was never received. If one or more of the S-NSSAIs used in the old registration area may not be served in the target registration area, the new AMF 155 may determine which PDU session may not be supported in the new registration area. The new AMF 155 may invoke the Namf_Communication_RegistrationCompleteNotify service operation including the rejected PDU session ID and a reject cause (e.g. the S-NSSAI becomes no longer available) towards the old AMF 155. The new AMF 155 may modify the PDU session status correspondingly. The old AMF 155 may inform the corresponding SMF 160(s) to locally release the UE's SM context by invoking the Nsmf_PDUSession_ReleaseSMContext service operation.

In an example, the new AMF 155 may send to the UE 100 an identity request/response 840 (e.g., PEI). If the PEI was not provided by the UE 100 nor retrieved from the old AMF 155, the identity request procedure may be initiated by AMF 155 sending an identity request message to the UE 100 to retrieve the PEI. The PEI may be transferred encrypted unless the UE 100 performs emergency registration and may not be authenticated. For an emergency registration, the UE 100 may have included the PEI in the registration request.

In an example, the new AMF 155 may initiate ME identity check 845 by invoking the N5g-eir_EquipmentIdentityCheck_Get service operation 845.

In an example, the new AMF 155, based on the SUPI, may select 905 a UDM 140. The UDM 140 may select a UDR instance. In an example, the AMF 155 may selects a UDM 140.

In an example, if the AMF 155 has changed since the last registration procedure, or if the UE 100 provides a SUPI which may not refer to a valid context in the AMF 155, or if the UE 100 registers to the same AMF 155 it has already registered to a non-3GPP access (e.g., the UE 100 is registered over a non-3GPP access and may initiate the registration procedure to add a 3GPP access), the new AMF 155 may register with the UDM 140 using Nudm_UECM_Registration 910 and may subscribe to be notified when the UDM 140 may deregister the AMF 155. The UDM 140 may store the AMF 155 identity associated to the access type and may not remove the AMF 155 identity associated to the other access type. The UDM 140 may store information provided at registration in UDR, by Nudr_UDM_Update. In an example, the AMF 155 may retrieve the access and mobility subscription data and SMF 160 selection subscription data using Nudm_SDM_Get 915. The UDM 140 may retrieve this information from UDR by Nudr_UDM_Query(access and mobility subscription data). After a successful response is received, the AMF 155 may subscribe to be notified using Nudm_SDM_Subscribe 920 when the data requested may be modified. The UDM 140 may subscribe to UDR by Nudr_UDM_Subscribe. The GPSI may be provided to the AMF 155 in the subscription data from the UDM 140 if the GPSI is available in the UE 100 subscription data. In an example, the new AMF 155 may provide the access type it serves for the UE 100 to the UDM 140 and the access type may be set to 3GPP access. The UDM 140 may store the associated access type together with the serving AMF 155 in UDR by Nudr_UDM_Update. The new AMF 155 may create an MM context for the UE 100 after getting the mobility subscription data from the UDM 140. In an example, when the UDM 140 stores the associated access type together with the serving AMF 155, the UDM 140 may initiate a Nudm_UECM_DeregistrationNotification 921 to the old AMF 155 corresponding to 3GPP access. The old AMF 155 may remove the MM context of the UE. If the serving NF removal reason indicated by the UDM 140 is initial registration, then the old AMF 155 may invoke the Namf_EventExposure_Notify service operation towards all the associated SMF 160 s of the UE 100 to notify that the UE 100 is deregistered from old AMF 155. The SMF 160 may release the PDU session(s) on getting this notification. In an example, the old AMF 155 may unsubscribe with the UDM 140 for subscription data using Nudm_SDM_unsubscribe 922.

In an example, if the AMF 155 decides to initiate PCF 135 communication, e.g. the AMF 155 has not yet obtained access and mobility policy for the UE 100 or if the access and mobility policy in the AMF 155 are no longer valid, the AMF 155 may select 925 a PCF 135. If the new AMF 155 receives a PCF ID from the old AMF 155 and successfully contacts the PCF 135 identified by the PCF ID, the AMF 155 may select the (V-)PCF identified by the PCF ID. If the PCF 135 identified by the PCF ID may not be used (e.g. no response from the PCF 135) or if there is no PCF ID received from the old AMF 155, the AMF 155 may select 925 a PCF 135.

In an example, the new AMF 155 may perform a policy association establishment 930 during registration procedure. If the new AMF 155 contacts the PCF 135 identified by the (V-) PCF ID received during inter-AMF 155 mobility, the new AMF 155 may include the PCF-ID in the Npcf_AMPolicyControl Get operation. If the AMF 155 notifies the mobility restrictions (e.g. UE 100 location) to the PCF 135 for adjustment, or if the PCF 135 updates the mobility restrictions itself due to some conditions (e.g. application in use, time and date), the PCF 135 may provide the updated mobility restrictions to the AMF 155.

In an example, the PCF 135 may invoke Namf_EventExposure_Subscribe service operation 935 for UE 100 event subscription.

In an example, the AMF 155 may send to the SMF 160 an Nsmf_PDUSession_UpdateSMContext 936. In an example, the AMF 155 may invoke the Nsmf_PDUSession_UpdateSMContext if the PDU session(s) to be re-activated is included in the registration request. The AMF 155 may send Nsmf_PDUSession_UpdateSMContext request to SMF 160(s) associated with the PDU session(s) to activate user plane connections of the PDU session(s). The SMF 160 may decide to trigger e.g. the intermediate UPF 110 insertion, removal or change of PSA. In the case that the intermediate UPF 110 insertion, removal, or relocation is performed for the PDU session(s) not included in PDU session(s) to be re-activated, the procedure may be performed without N11 and N2 interactions to update the N3 user plane between (R)AN 105 and 5GC. The AMF 155 may invoke the Nsmf_PDUSession_ReleaseSMContext service operation towards the SMF 160 if any PDU session status indicates that it is released at the UE 100. The AMF 155 may invoke the Nsmf_PDUSession_ReleaseSMContext service operation towards the SMF 160 in order to release any network resources related to the PDU session.

In an example, the new AMF 155 may send to a N3IWF an N2 AMF 155 mobility request 940. If the AMF 155 has changed, the new AMF 155 may create an NGAP UE 100 association towards the N3IWF to which the UE 100 is connected. In an example, the N3IWF may respond to the new AMF 155 with an N2 AMF 155 mobility response 940.

In an example, the new AMF 155 may send to the UE 100 a registration accept 955 (comprising: 5G-GUTI, registration area, mobility restrictions, PDU session status, allowed NSSAI, [mapping of allowed NSSAI], periodic registration update timer, LADN information and accepted MICO mode, IMS voice over PS session supported indication, emergency service support indicator, and/or the like). In an example, the AMF 155 may send the registration accept message to the UE 100 indicating that the registration request has been accepted. 5G-GUTI may be included if the AMF 155 allocates a new 5G-GUTI. If the AMF 155 allocates a new registration area, it may send the registration area to the UE 100 via registration accept message 955. If there is no registration area included in the registration accept message, the UE 100 may consider the old registration area as valid. In an example, mobility restrictions may be included in case mobility restrictions may apply for the UE 100 and registration type may not be emergency registration. The AMF 155 may indicate the established PDU sessions to the UE 100 in the PDU session status. The UE 100 may remove locally any internal resources related to PDU sessions that are not marked as established in the received PDU session status. In an example, when the UE 100 is connected to the two AMF 155 belonging to different PLMN via 3GPP access and non-3GPP access then the UE 100 may remove locally any internal resources related to the PDU session of the current PLMN that are not marked as established in received PDU session status. If the PDU session status information was in the registration request, the AMF 155 may indicate the PDU session status to the UE. The mapping of allowed NSSAI may be the mapping of each S-NSSAI of the allowed NSSAI to the S-NSSAIs of the configured NSSAI for the HPLMN. The AMF 155 may include in the registration accept message 955 the LADN information for LADNs that are available within the registration area determined by the AMF 155 for the UE. If the UE 100 included MICO mode in the request, then AMF 155 may respond whether MICO mode may be used. The AMF 155 may set the IMS voice over PS session supported Indication. In an example, in order to set the IMS voice over PS session supported indication, the AMF 155 may perform a UE/RAN radio information and compatibility request procedure to check the compatibility of the UE 100 and RAN radio capabilities related to IMS voice over PS. In an example, the emergency service support indicator may inform the UE 100 that emergency services are supported, e.g., the UE 100 may request PDU session for emergency services. In an example, the handover restriction list and UE-AMBR may be provided to NG-RAN by the AMF 155.

In an example, the UE 100 may send to the new AMF 155 a registration complete 960 message. In an example, the UE 100 may send the registration complete message 960 to the AMF 155 to acknowledge that a new 5G-GUTI may be assigned. In an example, when information about the PDU session(s) to be re-activated is not included in the registration request, the AMF 155 may release the signaling connection with the UE 100. In an example, when the follow-on request is included in the registration request, the AMF 155 may not release the signaling connection after the completion of the registration procedure. In an example, if the AMF 155 is aware that some signaling is pending in the AMF 155 or between the UE 100 and the 5GC, the AMF 155 may not release the signaling connection after the completion of the registration procedure.

As depicted in example FIG. 10 and FIG. 11, a service request procedure e.g., a UE 100 triggered service request procedure may be used by a UE 100 in CM-IDLE state to request the establishment of a secure connection to an AMF 155. FIG. 11 is continuation of FIG. 10 depicting the service request procedure. The service request procedure may be used to activate a user plane connection for an established PDU session. The service request procedure may be triggered by the UE 100 or the 5GC, and may be used when the UE 100 is in CM-IDLE and/or in CM-CONNECTED and may allow selectively to activate user plane connections for some of the established PDU sessions.

In an example, a UE 100 in CM IDLE state may initiate the service request procedure to send uplink signaling messages, user data, and/or the like, as a response to a network paging request, and/or the like. In an example, after receiving the service request message, the AMF 155 may perform authentication. In an example, after the establishment of signaling connection to the AMF 155, the UE 100 or network may send signaling messages, e.g. PDU session establishment from the UE 100 to a SMF 160, via the AMF 155.

In an example, for any service request, the AMF 155 may respond with a service accept message to synchronize PDU session status between the UE 100 and network. The AMF 155 may respond with a service reject message to the UE 100, if the service request may not be accepted by the network. The service reject message may include an indication or cause code requesting the UE 100 to perform a registration update procedure. In an example, for service request due to user data, network may take further actions if user plane connection activation may not be successful. In an example FIG. 10 and FIG. 11, more than one UPF, e.g., old UPF 110-2 and PDU session Anchor PSA UPF 110-3 may be involved.

In an example, the UE 100 may send to a (R)AN 105 an AN message comprising AN parameters, mobility management, MM NAS service request 1005 (e.g., list of PDU sessions to be activated, list of allowed PDU sessions, security parameters, PDU session status, and/or the like), and/or the like. In an example, the UE 100 may provide the list of PDU sessions to be activated when the UE 100 may re-activate the PDU session(s). The list of allowed PDU sessions may be provided by the UE 100 when the service request may be a response of a paging or a NAS notification, and may identify the PDU sessions that may be transferred or associated to the access on which the service request may be sent. In an example, for the case of NG-RAN, the AN parameters may include selected PLMN ID, and an establishment cause. The establishment cause may provide the reason for requesting the establishment of an RRC connection. The UE 100 may send NAS service request message towards the AMF 155 encapsulated in an RRC message to the RAN 105.

In an example, if the service request may be triggered for user data, the UE 100 may identify, using the list of PDU sessions to be activated, the PDU session(s) for which the UP connections are to be activated in the NAS service request message. If the service request may be triggered for signaling, the UE 100 may not identify any PDU session(s). If this procedure may be triggered for paging response, and/or the UE 100 may have at the same time user data to be transferred, the UE 100 may identify the PDU session(s) whose UP connections may be activated in MM NAS service request message, by the list of PDU sessions to be activated.

In an example, if the service request over 3GPP access may be triggered in response to a paging indicating non-3GPP access, the NAS service request message may identify in the list of allowed PDU sessions the list of PDU sessions associated with the non-3GPP access that may be re-activated over 3GPP. In an example, the PDU session status may indicate the PDU sessions available in the UE 100. In an example, the UE 100 may not trigger the service request procedure for a PDU session corresponding to a LADN when the UE 100 may be outside the area of availability of the LADN. The UE 100 may not identify such PDU session(s) in the list of PDU sessions to be activated, if the service request may be triggered for other reasons.

In an example, the (R)AN 105 may send to AMF 155 an N2 Message 1010 (e.g., a service request) comprising N2 parameters, MM NAS service request, and/or the like. The AMF 155 may reject the N2 message if it may not be able to handle the service request. In an example, if NG-RAN may be used, the N2 parameters may include the 5G-GUTI, selected PLMN ID, location information, RAT type, establishment cause, and/or the like. In an example, the 5G-GUTI may be obtained in RRC procedure and the (R)AN 105 may select the AMF 155 according to the 5G-GUTI. In an example, the location information and RAT type may relate to the cell in which the UE 100 may be camping. In an example, based on the PDU session status, the AMF 155 may initiate PDU session release procedure in the network for the PDU sessions whose PDU session ID(s) may be indicated by the UE 100 as not available.

In an example, if the service request was not sent integrity protected or integrity protection verification failed, the AMF 155 may initiate a NAS authentication/security procedure 1015.

In an example, if the UE 100 triggers the service request to establish a signaling connection, upon successful establishment of the signaling connection, the UE 100 and the network may exchange NAS signaling.

In an example the AMF 155 may send to the SMF 160 a PDU session update context request 1020 e.g., Nsmf_PDUSession_UpdateSMContext request comprising PDU session ID(s), Cause(s), UE 100 location information, access type, and/or the like.

In an example, the Nsmf_PDUSession_UpdateSMContext request may be invoked by the AMF 155 if the UE 100 may identify PDU session(s) to be activated in the NAS service request message. In an example, the Nsmf_PDUSession_UpdateSMContext request may be triggered by the SMF 160 wherein the PDU session(s) identified by the UE 100 may correlate to other PDU session ID(s) than the one triggering the procedure. In an example, the Nsmf_PDUSession_UpdateSMContext request may be triggered by the SMF 160 wherein the current UE 100 location may be outside the area of validity for the N2 information provided by the SMF 160 during a network triggered service request procedure. The AMF 155 may not send the N2 information provided by the SMF 160 during the network triggered service request procedure.

In an example, the AMF 155 may determine the PDU session(s) to be activated and may send an Nsmf_PDUSession_UpdateSMContext request to SMF 160(s) associated with the PDU session(s) with cause set to indicate establishment of user plane resources for the PDU session(s).

In an example, if the procedure may be triggered in response to paging indicating non-3GPP access, and the list of allowed PDU sessions provided by the UE 100 may not include the PDU session for which the UE 100 was paged, the AMF 155 may notify the SMF 160 that the user plane for the PDU session may not be re-activated. The service request procedure may succeed without re-activating the user plane of any PDU sessions, and the AMF 155 may notify the UE 100.

In an example, if the PDU session ID may correspond to a LADN and the SMF 160 may determine that the UE 100 may be outside the area of availability of the LADN based on the UE 100 location reporting from the AMF 155, the SMF 160 may decide to (based on local policies) keep the PDU session, may reject the activation of user plane connection for the PDU session and may inform the AMF 155. In an example, if the procedure may be triggered by a network triggered service request, the SMF 160 may notify the UPF 110 that originated the data notification to discard downlink data for the PDU sessions and/or to not provide further data notification messages. The SMF 160 may respond to the AMF 155 with an appropriate reject cause and the user plane activation of PDU session may be stopped.

In an example, if the PDU session ID may correspond to a LADN and the SMF 160 may determine that the UE 100 may be outside the area of availability of the LADN based on the UE 100 location reporting from the AMF 155, the SMF 160 may decide to (based on local policies) release the PDU session. The SMF 160 may locally release the PDU session and may inform the AMF 155 that the PDU session may be released. The SMF 160 may respond to the AMF 155 with an appropriate reject cause and the user plane Activation of PDU session may be stopped.

In an example, if the UP activation of the PDU session may be accepted by the SMF 160, based on the location info received from the AMF 155, the SMF 160 may check the UPF 110 Selection 1025 Criteria (e.g., slice isolation requirements, slice coexistence requirements, UPF's 110 dynamic load, UPF's 110 relative static capacity among UPFs supporting the same DNN, UPF 110 location available at the SMF 160, UE 100 location information, Capability of the UPF 110 and the functionality required for the particular UE 100 session. In an example, an appropriate UPF 110 may be selected by matching the functionality and features required for a UE 100, DNN, PDU session type (e.g. IPv4, IPv6, ethernet type or unstructured type) and if applicable, the static IP address/prefix, SSC mode selected for the PDU session, UE 100 subscription profile in UDM 140, DNAI as included in the PCC rules, local operator policies, S-NSSAI, access technology being used by the UE 100, UPF 110 logical topology, and/or the like), and may determine to perform one or more of the following: continue using the current UPF(s); may select a new intermediate UPF 110 (or add/remove an intermediate UPF 110), if the UE 100 has moved out of the service area of the UPF 110 that was previously connecting to the (R)AN 105, while maintaining the UPF(s) acting as PDU session anchor; may trigger re-establishment of the PDU session to perform relocation/reallocation of the UPF 110 acting as PDU session anchor, e.g. the UE 100 has moved out of the service area of the anchor UPF 110 which is connecting to RAN 105.

In an example, the SMF 160 may send to the UPF 110 (e.g., new intermediate UPF 110) an N4 session establishment request 1030. In an example, if the SMF 160 may select a new UPF 110 to act as intermediate UPF 110-2 for the PDU session, or if the SMF 160 may select to insert an intermediate UPF 110 for a PDU session which may not have an intermediate UPF 110-2, an N4 session establishment request 1030 message may be sent to the new UPF 110, providing packet detection, data forwarding, enforcement and reporting rules to be installed on the new intermediate UPF. The PDU session anchor addressing information (on N9) for this PDU session may be provided to the intermediate UPF 110-2.

In an example, if a new UPF 110 is selected by the SMF 160 to replace the old (intermediate) UPF 110-2, the SMF 160 may include a data forwarding indication. The data forwarding indication may indicate to the UPF 110 that a second tunnel endpoint may be reserved for buffered DL data from the old I-UPF.

In an example, the new UPF 110 (intermediate) may send to SMF 160 an N4 session establishment response message 1030. In case the UPF 110 may allocate CN tunnel info, the UPF 110 may provide DL CN tunnel info for the UPF 110 acting as PDU session anchor and UL CN tunnel info (e.g., CN N3 tunnel info) to the SMF 160. If the data forwarding indication may be received, the new (intermediate) UPF 110 acting as N3 terminating point may send DL CN tunnel info for the old (intermediate) UPF 110-2 to the SMF 160. The SMF 160 may start a timer, to release the resource in the old intermediate UPF 110-2.

In an example, if the SMF 160 may selects a new intermediate UPF 110 for the PDU session or may remove the old I-UPF 110-2, the SMF 160 may send N4 session modification request message 1035 to PDU session anchor, PSA UPF 110-3, providing the data forwarding indication and DL tunnel information from new intermediate UPF 110.

In an example, if the new intermediate UPF 110 may be added for the PDU session, the (PSA) UPF 110-3 may begin to send the DL data to the new I-UPF 110 as indicated in the DL tunnel information.

In an example, if the service request may be triggered by the network, and the SMF 160 may remove the old I-UPF 110-2 and may not replace the old I-UPF 110-2 with the new I-UPF 110, the SMF 160 may include the data forwarding indication in the request. The data forwarding indication may indicate to the (PSA) UPF 110-3 that a second tunnel endpoint may be reserved for buffered DL data from the old I-UPF 110-2. In this case, the PSA UPF 110-3 may begin to buffer the DL data it may receive at the same time from the N6 interface.

In an example, the PSA UPF 110-3 (PSA) may send to the SMF 160 an N4 session modification response 1035. In an example, if the data forwarding indication may be received, the PSA UPF 110-3 may become as N3 terminating point and may send CN DL tunnel info for the old (intermediate) UPF 110-2 to the SMF 160. The SMF 160 may start a timer, to release the resource in old intermediate UPF 110-2 if there is one.

In an example, the SMF 160 may send to the old UPF 110-2 an N4 session modification request 1045 (e.g., may comprise new UPF 110 address, new UPF 110 DL tunnel ID, and/or the like). In an example, if the service request may be triggered by the network, and/or the SMF 160 may remove the old (intermediate) UPF 110-2, the SMF 160 may send the N4 session modification request message to the old (intermediate) UPF 110-2, and may provide the DL tunnel information for the buffered DL data. If the SMF 160 may allocate new I-UPF 110, the DL tunnel information is from the new (intermediate) UPF 110 may act as N3 terminating point. If the SMF 160 may not allocate a new I-UPF 110, the DL tunnel information may be from the new UPF 110 (PSA) 110-3 acting as N3 terminating point. The SMF 160 may start a timer to monitor the forwarding tunnel. In an example, the old (intermediate) UPF 110-2 may send N4 session modification response message to the SMF 160.

In an example, if the I-UPF 110-2 may be relocated and forwarding tunnel was established to the new I-UPF 110, the old (intermediate) UPF 110-2 may forward its buffered data to the new (intermediate) UPF 110 acting as N3 terminating point. In an example, if the old I-UPF 110-2 may be removed and the new I-UPF 110 may not be assigned for the PDU session and forwarding tunnel may be established to the UPF 110 (PSA) 110-3, the old (intermediate) UPF 110-2 may forward its buffered data to the UPF 110 (PSA) 110-3 acting as N3 terminating point.

In an example, the SMF 160 may send to the AMF 155 an N11 message 1060 e.g., a Nsmf_PDUSession_UpdateSMContext response (comprising: N1 SM container (PDU session ID, PDU session re-establishment indication), N2 SM information (PDU session ID, QoS profile, CN N3 tunnel info, S-NSSAI), Cause), upon reception of the Nsmf_PDUSession_UpdateSMContext request with a cause including e.g., establishment of user plane resources. The SMF 160 may determine whether UPF 110 reallocation may be performed, based on the UE 100 location information, UPF 110 service area and operator policies. In an example, for a PDU session that the SMF 160 may determine to be served by the current UPF 110, e.g., PDU session anchor or intermediate UPF, the SMF 160 may generate N2 SM information and may send an Nsmf_PDUSession_UpdateSMContext response 1060 to the AMF 155 to establish the user plane(s). The N2 SM information may contain information that the AMF 155 may provide to the RAN 105. In an example, for a PDU session that the SMF 160 may determine as requiring a UPF 110 relocation for PDU session anchor UPF, the SMF 160 may reject the activation of UP of the PDU session by sending Nsmf_PDUSession_UpdateSMContext response that may contain N1 SM container to the UE 100 via the AMF 155. The N1 SM container may include the corresponding PDU session ID and PDU session re-establishment indication.

Upon reception of the Namf_EventExposure_Notify from the AMF 155 to the SMF 160, with an indication that the UE 100 is reachable, if the SMF 160 may have pending DL data, the SMF 160 may invoke the Namf_Communication_N1N2MessageTransfer service operation to the AMF 155 to establish the user plane(s) for the PDU sessions. In an example, the SMF 160 may resume sending DL data notifications to the AMF 155 in case of DL data.

In an example, the SMF 160 may send a message to the AMF 155 to reject the activation of UP of the PDU session by including a cause in the Nsmf_PDUSession_UpdateSMContext response if the PDU session may correspond to a LADN and the UE 100 may be outside the area of availability of the LADN, or if the AMF 155 may notify the SMF 160 that the UE 100 may be reachable for regulatory prioritized service, and the PDU session to be activated may not for a regulatory prioritized service; or if the SMF 160 may decide to perform PSA UPF 110-3 relocation for the requested PDU session.

In an example, the AMF 155 may send to the (R)AN 105 an N2 request message 1065 (e.g., N2 SM information received from SMF 160, security context, AMF 155 signaling connection ID, handover restriction list, MM NAS service accept, list of recommended cells/TAs/NG-RAN node identifiers). In an example, the RAN 105 may store the security context, AMF 155 signaling connection Id, QoS information for the QoS flows of the PDU sessions that may be activated and N3 tunnel IDs in the UE 100 RAN 105 context. In an example, the MM NAS service accept may include PDU session status in the AMF 155. If the activation of UP of a PDU session may be rejected by the SMF 160, the MM NAS service accept may include the PDU session ID and the reason why the user plane resources may not be activated (e.g. LADN not available). Local PDU session release during the session request procedure may be indicated to the UE 100 via the session Status.

In an example, if there are multiple PDU sessions that may involve multiple SMF 160 s, the AMF 155 may not wait for responses from all SMF 160 s before it may send N2 SM information to the UE 100. The AMF 155 may wait for all responses from the SMF 160 s before it may send MM NAS service accept message to the UE 100.

In an example, the AMF 155 may include at least one N2 SM information from the SMF 160 if the procedure may be triggered for PDU session user plane activation. AMF 155 may send additional N2 SM information from SMF 160 s in separate N2 message(s) (e.g. N2 tunnel setup request), if there is any. Alternatively, if multiple SMF 160 s may be involved, the AMF 155 may send one N2 request message to (R)AN 105 after all the Nsmf_PDUSession_UpdateSMContext response service operations from all the SMF 160 s associated with the UE 100 may be received. In such case, the N2 request message may include the N2 SM information received in each of the Nsmf_PDUSession_UpdateSMContext response and PDU session ID to enable AMF 155 to associate responses to relevant SMF 160.

In an example, if the RAN 105 (e.g., NG RAN) node may provide the list of recommended cells/TAs/NG-RAN node identifiers during the AN release procedure, the AMF 155 may include the information from the list in the N2 request. The RAN 105 may use this information to allocate the RAN 105 notification area when the RAN 105 may decide to enable RRC inactive state for the UE 100.

If the AMF 155 may receive an indication, from the SMF 160 during a PDU session establishment procedure that the UE 100 may be using a PDU session related to latency sensitive services, for any of the PDU sessions established for the UE 100 and the AMF 155 has received an indication from the UE 100 that may support the CM-CONNECTED with RRC inactive state, then the AMF 155 may include the UE's RRC inactive assistance information. In an example, the AMF 155 based on network configuration, may include the UE's RRC inactive assistance information.

In an example, the (R)AN 105 may send to the UE 100 a message to perform RRC connection reconfiguration 1070 with the UE 100 depending on the QoS information for all the QoS flows of the PDU sessions whose UP connections may be activated and data radio bearers. In an example, the user plane security may be established.

In an example, if the N2 request may include a MM NAS service accept message, the RAN 105 may forward the MM NAS service accept to the UE 100. The UE 100 may locally delete context of PDU sessions that may not be available in 5GC.

In an example, if the N1 SM information may be transmitted to the UE 100 and may indicate that some PDU session(s) may be re-established, the UE 100 may initiate PDU session re-establishment for the PDU session(s) that may be re-established after the service request procedure may be complete.

In an example, after the user plane radio resources may be setup, the uplink data from the UE 100 may be forwarded to the RAN 105. The RAN 105 (e.g., NG-RAN) may send the uplink data to the UPF 110 address and tunnel ID provided.

In an example, the (R)AN 105 may send to the AMF 155 an N2 request Ack 1105 (e.g., N2 SM information (comprising: AN tunnel info, list of accepted QoS flows for the PDU sessions whose UP connections are activated, list of rejected QoS flows for the PDU sessions whose UP connections are activated)). In an example, the N2 request message may include N2 SM information(s), e.g. AN tunnel info. RAN 105 may respond N2 SM information with separate N2 message (e.g. N2 tunnel setup response). In an example, if multiple N2 SM information are included in the N2 request message, the N2 request Ack may include multiple N2 SM information and information to enable the AMF 155 to associate the responses to relevant SMF 160.

In an example, the AMF 155 may send to the SMF 160 a Nsmf_PDUSession_UpdateSMContext request 1110 (N2 SM information (AN tunnel info), RAT type) per PDU session. If the AMF 155 may receive N2 SM information (one or multiple) from the RAN 105, then the AMF 155 may forward the N2 SM information to the relevant SMF 160. If the UE 100 time zone may change compared to the last reported UE 100 Time Zone then the AMF 155 may include the UE 100 time zone IE in the Nsmf_PDUSession_UpdateSMContext request message.

In an example, if dynamic PCC is deployed, the SMF 160 may initiate notification about new location information to the PCF 135 (if subscribed) by invoking an event exposure notification operation (e.g., a Nsmf_EventExposure_Notify service operation). The PCF 135 may provide updated policies by invoking a policy control update notification message 1115 (e.g., a Npcf_SMPolicyControl_UpdateNotify operation).

In an example, if the SMF 160 may select a new UPF 110 to act as intermediate UPF 110 for the PDU session, the SMF 160 may initiates an N4 session modification procedure 1120 to the new I-UPF 110 and may provide AN tunnel info. The downlink data from the new I-UPF 110 may be forwarded to RAN 105 and UE 100. In an example, the UPF 110 may send to the SMF 160, an N4 session modification response 1120. In an example, the SMF 160 may send to the AMF 155, an Nsmf_PDUSession_UpdateSMContext response 1140.

In an example, if forwarding tunnel may be established to the new I-UPF 110 and if the timer SMF 160 set for forwarding tunnel may be expired, the SMF 160 may sends N4 session modification request 1145 to new (intermediate) UPF 110 acting as N3 terminating point to release the forwarding tunnel. In an example, the new (intermediate) UPF 110 may send to the SMF 160 an N4 session modification response 1145. In an example, the SMF 160 may send to the PSA UPF 110-3 an N4 session modification request 1150, or N4 session release request. In an example, if the SMF 160 may continue using the old UPF 110-2, the SMF 160 may send an N4 session modification request 1155, providing AN tunnel info. In an example, if the SMF 160 may select a new UPF 110 to act as intermediate UPF 110, and the old UPF 110-2 may not be PSA UPF 110-3, the SMF 160 may initiate resource release, after timer expires, by sending an N4 session release request (release cause) to the old intermediate UPF 110-2.

In an example, the old intermediate UPF 110-2 may send to the SMF 160 an N4 session modification response or N4 session release response 1155. The old UPF 110-2 may acknowledge with the N4 session modification response or N4 session release response message to confirm the modification or release of resources. The AMF 155 may invoke the Namf_EventExposure_Notify service operation to notify the mobility related events, after this procedure may complete, towards the NFs that may have subscribed for the events. In an example, the AMF 155 may invoke the Namf_EventExposure_Notify towards the SMF 160 if the SMF 160 had subscribed for UE 100 moving into or out of area of interest and if the UE's current location may indicate that it may be moving into or moving outside of the area of interest subscribed, or if the SMF 160 had subscribed for LADN DNN and if the UE 100 may be moving into or outside of an area where the LADN is available, or if the UE 100 may be in MICO mode and the AMF 155 had notified an SMF 160 of the UE 100 being unreachable and that SMF 160 may not send DL data notifications to the AMF 155, and the AMF 155 may informs the SMF 160 that the UE 100 is reachable, or if the SMF 160 had subscribed for UE 100 reachability status, then the AMF 155 may notify the UE 100 reachability.

An example PDU session establishment procedure depicted in FIG. 12 and FIG. 13. In an example embodiment, when the PDU session establishment procedure may be employed, the UE 100 may send to the AMF 155 a NAS Message 1205 (or a SM NAS message) comprising NSSAI, S-NSSAI (e.g., requested S-NSSAI, allowed S-NSSAI, subscribed S-NSSAI, and/or the like), DNN, PDU session ID, request type, old PDU session ID, N1 SM container (PDU session establishment request), and/or the like. In an example, the UE 100, in order to establish a new PDU session, may generate a new PDU session ID. In an example, when emergency service may be required and an emergency PDU session may not already be established, the UE 100 may initiate the UE 100 requested PDU session establishment procedure with a request type indicating emergency request. In an example, the UE 100 may initiate the UE 100 requested PDU session establishment procedure by the transmission of the NAS message containing a PDU session establishment request within the N1 SM container. The PDU session establishment request may include a PDU type, SSC mode, protocol configuration options, and/or the like. In an example, the request type may indicate initial request if the PDU session establishment is a request to establish the new PDU session and may indicate existing PDU session if the request refers to an existing PDU session between 3GPP access and non-3GPP access or to an existing PDN connection in EPC. In an example, the request type may indicate emergency request if the PDU session establishment may be a request to establish a PDU session for emergency services. The request type may indicate existing emergency PDU session if the request refers to an existing PDU session for emergency services between 3GPP access and non-3GPP access. In an example, the NAS message sent by the UE 100 may be encapsulated by the AN in a N2 message towards the AMF 155 that may include user location information and access technology type information. In an example, the PDU session establishment request message may contain SM PDU DN request container containing information for the PDU session authorization by the external DN. In an example, if the procedure may be triggered for SSC mode 3 operation, the UE 100 may include the old PDU session ID which may indicate the PDU session ID of the on-going PDU session to be released, in the NAS message. The old PDU session ID may be an optional parameter which may be included in this case. In an example, the AMF 155 may receive from the AN the NAS message (e.g., NAS SM message) together with user location information (e.g. cell ID in case of the RAN 105). In an example, the UE 100 may not trigger a PDU session establishment for a PDU session corresponding to a LADN when the UE 100 is outside the area of availability of the LADN.

In an example, the AMF 155 may determine that the NAS message or the SM NAS message may correspond to the request for the new PDU session based on that request type indicates initial request and that the PDU session ID may not be used for any existing PDU session(s) of the UE 100. If the NAS message does not contain an S-NSSAI, the AMF 155 may determine a default S-NSSAI for the requested PDU session either according to the UE 100 subscription, if it may contain only one default S-NSSAI, or based on operator policy. In an example, the AMF 155 may perform SMF 160 selection 1210 and select an SMF 160. If the request type may indicate initial request or the request may be due to handover from EPS, the AMF 155 may store an association of the S-NSSAI, the PDU session ID and a SMF 160 ID. In an example, if the request type is initial request and if the old PDU session ID indicating the existing PDU session may be contained in the message, the AMF 155 may select the SMF 160 and may store an association of the new PDU session ID and the selected SMF 160 ID.

In an example, the AMF 155 may send to the SMF 160, an N11 message 1215, e.g., Nsmf_PDUSession_CreateSMContext request (comprising: SUPI or PEI, DNN, S-NSSAI, PDU session ID, AMF 155 ID, request type, N1 SM container (PDU session establishment request), user location information, access type, PEI, GPSI), or Nsmf_PDUSession_UpdateSMContext request (SUPI, DNN, S-NSSAI, PDU session ID, AMF 155 ID, request type, N1 SM container (PDU session establishment request), user location information, access type, RAT type, PEI). In an example, if the AMF 155 may not have an association with the SMF 160 for the PDU session ID provided by the UE 100 (e.g when request type indicates initial request), the AMF 155 may invoke the Nsmf_PDUSession_CreateSMContext request, but if the AMF 155 already has an association with an SMF 160 for the PDU session ID provided by the UE 100 (e.g when request type indicates existing PDU session), the AMF 155 may invoke the Nsmf_PDUSession_UpdateSMContext request. In an example, the AMF 155 ID may be the UE's GUAMI which uniquely identifies the AMF 155 serving the UE 100. The AMF 155 may forward the PDU session ID together with the N1 SM container containing the PDU session establishment request received from the UE 100. The AMF 155 may provide the PEI instead of the SUPI when the UE 100 has registered for emergency services without providing the SUPI. In case the UE 100 has registered for emergency services but has not been authenticated, the AMF 155 may indicate that the SUPI has not been authenticated.

In an example, if the request type may indicate neither emergency request nor existing emergency PDU session and, if the SMF 160 has not yet registered and subscription data may not be available, the SMF 160 may register with the UDM 140, and may retrieve subscription data 1225 and subscribes to be notified when subscription data may be modified. In an example, if the request type may indicate existing PDU session or existing emergency PDU session, the SMF 160 may determine that the request may be due to handover between 3GPP access and non-3GPP access or due to handover from EPS. The SMF 160 may identify the existing PDU session based on the PDU session ID. The SMF 160 may not create a new SM context but instead may update the existing SM context and may provide the representation of the updated SM context to the AMF 155 in the response. if the request type may be initial request and if the old PDU session ID may be included in Nsmf_PDUSession_CreateSMContext request, the SMF 160 may identify the existing PDU session to be released based on the old PDU session ID.

In an example, the SMF 160 may send to the AMF 155, the N11 message response 1220, e.g., either a PDU session create/update response, Nsmf_PDUSession_CreateSMContext response 1220 (cause, SM context ID or N1 SM container (PDU session reject(cause))) or an Nsmf_PDUSession_UpdateSMContext response.

In an example, if the SMF 160 may perform secondary authorization/authentication 1230 during the establishment of the PDU session by a DN-AAA server, the SMF 160 may select a UPF 110 and may trigger a PDU session establishment authentication/authorization.

In an example, if the request type may indicate initial request, the SMF 160 may select an SSC mode for the PDU session. The SMF 160 may select one or more UPFs as needed. In case of PDU type IPv4 or IPv6, the SMF 160 may allocate an IP address/prefix for the PDU session. In case of PDU type IPv6, the SMF 160 may allocate an interface identifier to the UE 100 for the UE 100 to build its link-local address. For Unstructured PDU type the SMF 160 may allocate an IPv6 prefix for the PDU session and N6 point-to-point tunneling (based on UDP/IPv6).

In an example, if dynamic PCC is deployed, the may SMF 160 performs PCF 135 selection 1235. If the request type indicates existing PDU session or existing emergency PDU session, the SMF 160 may use the PCF 135 already selected for the PDU session. If dynamic PCC is not deployed, the SMF 160 may apply local policy.

In an example, the SMF 160 may perform a session management policy establishment procedure 1240 to establish a PDU session with the PCF 135 and may get the default PCC Rules for the PDU session. The GPSI may be included if available at the SMF 160. If the request type in 1215 indicates existing PDU session, the SMF 160 may notify an event previously subscribed by the PCF 135 by a session management policy modification procedure and the PCF 135 may update policy information in the SMF 160. The PCF 135 may provide authorized session-AMBR and the authorized 5QI and ARP to SMF 160. The PCF 135 may subscribe to the IP allocation/release event in the SMF 160 (and may subscribe other events).

In an example, the PCF 135, based on the emergency DNN, may set the ARP of the PCC rules to a value that may be reserved for emergency services.

In an example, if the request type in 1215 indicates initial request, the SMF 160 may select an SSC mode for the PDU session. The SMF 160 may select 1245 one or more UPFs as needed. In case of PDU type IPv4 or IPv6, the SMF 160 may allocate an IP address/prefix for the PDU session. In case of PDU type IPv6, the SMF 160 may allocate an interface identifier to the UE 100 for the UE 100 to build its link-local address. For unstructured PDU type the SMF 160 may allocate an IPv6 prefix for the PDU session and N6 point-to-point tunneling (e.g., based on UDP/IPv6). In an example, for Ethernet PDU type PDU session, neither a MAC nor an IP address may be allocated by the SMF 160 to the UE 100 for this PDU session.

In an example, if the request type in 1215 is existing PDU session, the SMF 160 may maintain the same IP address/prefix that may be allocated to the UE 100 in the source network.

In an example, if the request type in 1215 indicates existing PDU session referring to an existing PDU session moved between 3GPP access and non-3GPP access, the SMF 160 may maintain the SSC mode of the PDU session, e.g., the current PDU session Anchor and IP address. In an example, the SMF 160 may trigger e.g. new intermediate UPF 110 insertion or allocation of a new UPF 110. In an example, if the request type indicates emergency request, the SMF 160 may select 1245 the UPF 110 and may select SSC mode 1.

In an example, the SMF 160 may perform a session management policy modification 1250 procedure to report some event to the PCF 135 that has previously subscribed. If request type is initial request and dynamic PCC is deployed and PDU type is IPv4 or IPv6, the SMF 160 may notify the PCF 135 (that has previously subscribed) with the allocated UE 100 IP address/prefix.

In an example, the PCF 135 may provide updated policies to the SMF 160. The PCF 135 may provide authorized session-AMBR and the authorized 5QI and ARP to the SMF 160.

In an example, if request type indicates initial request, the SMF 160 may initiate an N4 session establishment procedure 1255 with the selected UPF 110. The SMF 160 may initiate an N4 session modification procedure with the selected UPF 110. In an example, the SMF 160 may send an N4 session establishment/modification request 1255 to the UPF 110 and may provide packet detection, enforcement, reporting rules, and/or the like to be installed on the UPF 110 for this PDU session. If CN tunnel info is allocated by the SMF 160, the CN tunnel info may be provided to the UPF 110. If the selective user plane deactivation is required for this PDU session, the SMF 160 may determine the Inactivity Timer and may provide it to the UPF 110. In an example, the UPF 110 may acknowledges by sending an N4 session establishment/modification response 1255. If CN tunnel info is allocated by the UPF, the CN tunnel info may be provided to SMF 160. In an example, if multiple UPFs are selected for the PDU session, the SMF 160 may initiate N4 session establishment/modification procedure 1255 with each UPF 110 of the PDU session.

In an example, the SMF 160 may send to the AMF 155 an Namf_Communication_N1N2MessageTransfer 1305 message (comprising PDU session ID, access type, N2 SM information (PDU session ID, QFI(s), QoS profile(s), CN tunnel info, S-NSSAI, session-AMBR, PDU session type, and/or the like), N1 SM container (PDU session establishment accept (QoS Rule(s), selected SSC mode, S-NSSAI, allocated IPv4 address, interface identifier, session-AMBR, selected PDU session type, and/or the like))). In case of multiple UPFs are used for the PDU session, the CN tunnel info may comprise tunnel information related with the UPF 110 that terminates N3. In an example, the N2 SM information may carry information that the AMF 155 may forward to the (R)AN 105 (e.g., the CN tunnel info corresponding to the core network address of the N3 tunnel corresponding to the PDU session, one or multiple QoS profiles and the corresponding QFIs may be provided to the (R)AN 105, the PDU session ID may be used by AN signaling with the UE 100 to indicate to the UE 100 the association between AN resources and a PDU session for the UE100, and/or the like). In an example, a PDU session may be associated to an S-NSSAI and a DNN. In an example, the N1 SM container may contain the PDU session establishment accept that the AMF 155 may provide to the UE 100. In an example, multiple QoS rules and QoS profiles may be included in the PDU session establishment accept within the N1 SM and in the N2 SM information. In an example, the Namf_Communication_N1N2MessageTransfer 1305 may further comprise the PDU session ID and information allowing the AMF 155 to know which access towards the UE 100 to use.

In an example, the AMF 155 may send to the (R)AN105 an N2 PDU session request 1310 (comprising N2 SM information, NAS message (PDU session ID, N1 SM container (PDU session establishment accept, and/or the like))). In an example, the AMF 155 may send the NAS message 1310 that may comprise PDU session ID and PDU session establishment accept targeted to the UE 100 and the N2 SM information received from the SMF 160 within the N2 PDU session request 1310 to the (R)AN 105.

In an example, the (R)AN 105 may issue AN specific signaling exchange 1315 with the UE 100 that may be related with the information received from SMF 160. In an example, in case of a 3GPP RAN 105, an RRC connection reconfiguration procedure may take place with the UE 100 to establish the necessary RAN 105 resources related to the QoS Rules for the PDU session request 1310. In an example, (R)AN 105 may allocate (R)AN 105 N3 tunnel information for the PDU session. In case of dual connectivity, the master RAN 105 node may assign some (zero or more) QFIs to be setup to a master RAN 105 node and others to the secondary RAN 105 node. The AN tunnel info may comprise a tunnel endpoint for each involved RAN 105 node, and the QFIs assigned to each tunnel endpoint. A QFI may be assigned to either the master RAN 105 node or the secondary RAN 105 node. In an example, (R)AN 105 may forward the NAS message 1310 (PDU session ID, N1 SM container (PDU session establishment accept)) to the UE 100. The (R)AN 105 may provide the NAS message to the UE 100 if the necessary RAN 105 resources are established and the allocation of (R)AN 105 tunnel information are successful.

In an example, the N2 PDU session response 1320 may comprise a PDU session ID, cause, N2 SM information (PDU session ID, AN tunnel info, list of accepted/rejected QFI(s)), and/or the like. In an example, the AN tunnel info may correspond to the access network address of the N3 tunnel corresponding to the PDU session.

In an example, the AMF 155 may forward the N2 SM information received from (R)AN 105 to the SMF 160 via a Nsmf_PDUSession_UpdateSMContext request 1330 (comprising: N2 SM information, request type, and/or the like). In an example, if the list of rejected QFI(s) is included in N2 SM information, the SMF 160 may release the rejected QFI(s) associated QoS profiles.

In an example, the SMF 160 may initiate an N4 session modification procedure 1335 with the UPF110. The SMF 160 may provide AN tunnel info to the UPF 110 as well as the corresponding forwarding rules. In an example, the UPF 110 may provide an N4 session modification response 1335 to the SMF 160160.

In an example, the SMF 160 may send to the AMF 155 an Nsmf_PDUSession_UpdateSMContext response 1340 (Cause). In an example, the SMF 160 may subscribe to the UE 100 mobility event notification from the AMF 155 (e.g. location reporting, UE 100 moving into or out of area of interest), after this step by invoking Namf_EventExposure_Subscribe service operation. For LADN, the SMF 160 may subscribe to the UE 100 moving into or out of LADN service area event notification by providing the LADN DNN as an indicator for the area of interest. The AMF 155 may forward relevant events subscribed by the SMF 160.

In an example, the SMF 160 may send to the AMF 155, a Nsmf_PDUSession_SMContextStatusNotify (release) 1345. In an example, if during the procedure, any time the PDU session establishment is not successful, the SMF 160 may inform the AMF 155 by invoking Nsmf_PDUSession_SMContextStatusNotify(release) 1345. The SMF 160 may releases any N4 session(s) created, any PDU session address if allocated (e.g IP address) and may release the association with the PCF 135.

In an example, in case of PDU type IPv6, the SMF 160 may generate an IPv6 Router Advertisement 1350 and may send it to the UE 100 via N4 and the UPF 110.

In an example, if the PDU session may not be established, the SMF 160 may unsubscribe 1360 to the modifications of session management subscription data for the corresponding (SUPI, DNN, S-NSSAI), using Nudm_SDM_Unsubscribe (SUPI, DNN, S-NSSAI), if the SMF 160 is no more handling a PDU session of the UE 100 for this (DNN, S-NSSAI). In an example, if the PDU session may not be established, the SMF 160 may deregister 1360 for the given PDU session using Nudm_UECM_Deregistration (SUPI, DNN, PDU session ID).

As depicted in FIG. 14, a connection management (CM) state may be related to a radio resource control (RRC) state. RRC-INACTIVE (e.g. RRC inactive) may be a state where a UE (e.g. a wireless device, device) remains in CM-CONNECTED (e.g. CM connected). In an example, the UE may move within an area configured by a RAN (e.g. NG-RAN), referred to as a RAN notification area (RNA), without notifying the RAN. In RRC_INACTIVE state, the last base station (e.g., gNB) of a RAN to serve the UE may keep the UE context and the UE-associated connection with the serving AMF and UPF (e.g. N2 connection, N3 connection). In an example, a UE in CM-IDLE may be in RRC-IDLE. In an example, a UE in CM-CONNECTED may be in RRC-CONNECTED. The mobility behavior of the UE in RRC-INACTIVE may be similar with RRC-IDLE state behavior (e.g. cell reselection based on serving cell quality, paging monitoring, periodic system information acquisition) and may apply different parameter for RRC-IDLE and RRC-INACTIVE.

FIG. 15 illustrates an example call flow for four RRC state transitions in accordance with embodiments of the present disclosure. The four RRC state transitions include: RRC-IDLE to RRC-CONNECTED; RRC-CONNECTED to RRC-INACTIVE; RRC-INACTIVE to RRC-CONNECTED; and RRC_CONNECTED to RRC-IDLE. It should be noted that, although the four RRC state transitions are shown as part of a single call flow diagram, each RRC state transition call flow can be performed independently from each other.

Starting with the RRC state transition from RRC-IDLE to RRC-CONNECTED, a UE in RRC-IDLE may send an RRC setup request message to an NG-RAN node (e.g., a gNB) to request RRC connection setup with the NG-RAN. The UE may receive an RRC setup message from the NG-RAN node in response to the RRC setup request message. The UE may transition from the RRC-IDLE to RRC-CONNECTED in response to the RRC setup message from the NG-RAN node. The RRC state maintained at the UE may be updated to reflect that the current RRC state of the UE is RRC-CONNECTED after the state transition. The UE may respond to the RRC setup message by sending an RRC setup complete message to the NG-RAN. The RRC state maintained at the NG-RAN node may be updated to reflect that the current RRC state of the UE is RRC-CONNECTED after receiving the RRC setup complete message.

For the RRC state transition from RRC-CONNECTED to RRC-INACTIVE, the NG-RAN node may send an RRC release message to the UE to request suspension of an RRC connection. In an example, the RRC release message may include suspend information that indicates to the UE that the RRC release message is for suspending instead of releasing the RRC connection. The suspend information may comprise a radio network temporary identity (RNTI) value, a radio access network (RAN) paging cycle, RAN notification area information, and/or the like. The UE may transition from RRC-CONNECTED to RRC-INACTIVE in response to the RRC release message from the NG-RAN node. The RRC state maintained at both the UE and the NG-RAN node may be updated to reflect that the current RRC state of the UE is RRC-INACTIVE.

For the RRC state transition from RRC-INACTIVE to RRC-CONNECTED, the UE may send an RRC resume request message to the NG-RAN node to request that the suspended RRC connection be resumed. The UE may receive an RRC resume message from the NG-RAN node in response to the RRC resume request message. In response to the RRC resume message from the NG-RAN node, the UE may transition from RRC-INANCTIVE to RRC-CONNECTED state and may send an RRC resume complete message to the NG-RAN node. The RRC state maintained at the UE may be updated to reflect that the current RRC state of the UE is RRC-CONNECTED after the state transition. The RRC state maintained at the NG-RAN node may be updated to reflect that the current RRC state of the UE is RRC-CONNECTED after receiving the RRC resume complete message from the UE.

Finally, for the RRC state transition from RRC-CONNECTED to RRC-IDLE, the NG-RAN node may send an RRC release message to the UE to request that the RRC connection be released. The UE may transition from RRC-CONNECTED to RRC-IDLE after receiving RRC release message from the NG-RAN node. The RRC state maintained at both the UE and the NG-RAN node may be updated to reflect that the current RRC state of the UE is RRC-IDLE.

A 5G core network node may query a NG-RAN node to get RRC state transition information of a UE. In an example, the core network may be an AMF. The AMF may send a UE state transition notification request message (e.g. UE state transition notification request message, RRC state notification message) to a NG-RAN node, requesting to report the RRC state transition information as illustrated in FIG. 16. The UE state transition notification request message may comprise AMF UE NGAP ID, RAN UE NGAP ID, an RRC Inactive Transition Report Request information element (IE) and/or the like. The AMF UE NGAP ID may uniquely identify a UE association over the NG interface (e.g. N2 interface) within the AMF side. The RAN UE NGAP ID may uniquely identify a UE association over the NG interface within the NG-RAN side. The RRC Inactive Transition Report Request IE may indicate a condition of RRC state transition reporting and may comprise a subsequent state transition report, single RRC connected state report, cancel report and/or the like.

In an example, the NG-RAN may report to the AMF by sending a UE notification message (e.g RRC_INACTIVE TRANSITION REPORT, RRC state information message) comprising an RRC state of the UE if the UE transition into RRC-CONNECTED from RRC-INACTIVE or vice versa in case the RRC Inactive Transition Report Request information element (IE) is set to “subsequent state transition report”. In an example, the NG-RAN may report to the AMF by sending the UE notification message but no subsequent UE notification messages if the UE is in RRC_CONNECTED state and the RRC Inactive Transition Report Request IE is set to “single RRC connected state report”. In an example, the NG-RAN may report to the AMF one UE notification message plus one subsequent UE notification message when the RRC state transitions to RRC_CONNECTED state if the UE is in RRC_INACTIVE state and the RRC Inactive Transition Report Request IE is set to “single RRC connected state report”. In an example, the NG-RAN may stop reporting to the AMF the RRC state of the UE in case the RRC Inactive Transition Report Request IE is set to “cancel report”. In an example, the UE notification message may further comprise AMF UE NGAP ID, RAN UE NGAP ID, user location information and/or the like. The user location information may comprise a tracking area identity, a cell global identity, an age of location (e.g. time stamp information as defined in IETF RFC 5905) of the location information and/or the like. The reporting of RRC state transitions may be requested per UE by the AMF. The continuous reporting by setting “subsequent state transition report” of all RRC state transitions can be enabled by operator local configuration.

A UE (e.g., a mobile or non-mobile wireless device) in an idle state may activate a mobile initiated communication only (MICO) mode to reduce power consumption. While the UE is in the idle state and the MICO mode is activated, the UE may transition to a connected state (e.g., a core network connected state) based on the UE initiating a data transfer or signaling (e.g. after a periodic registration update/TAU/RAU procedure) but may not transition to the connected state based on data transfers or signaling to the UE initiated by the network. As a result, the UE may not monitor (or even need to monitor) for paging messages from the network or perform cell reselection while the UE is in the idle state and the MICO mode is activated, thereby reducing power consumption of the UE. In addition, the UE may stop access stratum procedures while in the idle state and the MICO mode is activated to further reduce power consumption of the UE.

A UE using the MICO mode may be reachable and available for mobile terminating services during the time the UE is in a connected state and for a period of time, referred to as an active time, after the UE transitions from the connected state. As a result, the MICO mode may be intended for use by UEs that expect infrequent mobile terminating communications and/or that may tolerate relatively high latency for mobile terminating communications. High latency may refer to a scenario where an initial response time, before normal exchange of packets is established, is higher than a per-defined time period, e.g., 2-ms, 1-s, 10-s, and/or the like.

In an example, a UE and an AMF may negotiate the use of MICO mode during a registration procedure. For example, the UE may indicate a preference for MICO mode during a time duration of the registration procedure, such as during an initial registration or during a mobility registration update procedure with the AMF. The AMF may determine whether the MICO mode is acceptable for the UE. In an example, the AMF may accept the MICO mode for the UE and may indicate the acceptance by including a MICO indication in a registration accept message to the UE.

In an example, the AMF may assign a registration area to the UE during the registration procedure. When the AMF indicates MICO mode to a UE, the registration area may not be constrained by paging area size. In an example, if the AMF serving area is the whole PLMN, the AMF may decide to provide an “all PLMN” registration area to the UE based on local policy and subscription information. In such a case, re-registration to the same PLMN due to mobility may not apply. In an example, the AMF may assign “all PLMN” if the AMF supports whole PLMN area.

In an example, when the AMF indicates/marks MICO mode to the UE, the AMF may consider the UE unreachable during a time duration that the UE CM state in the AMF is CM-IDLE state. In an example, the AMF may reject any request for downlink data delivery for the UE in MICO mode and whose UE CM state in the AMF is CM-IDLE with an appropriate cause.

In an example, the UE in MICO mode may be reachable for mobile terminated data or signaling when the UE is in CM-CONNECTED/RRC-CONNECTED.

In an example, the UE in MICO mode may not monitor (or need to monitor) for paging messages from the network during a time duration that the UE is in CM-IDLE.

FIG. 17 illustrates an example call flow of a negotiation of MICO mode and activation and deactivation of MICO mode between a UE and a 5G network.

In an example, the UE may indicate a preference or need for MICO mode during a registration procedure by sending a registration request message. The registration request message may comprise an indication indicating the MICO mode to an AMF. The AMF may accept the use of MICO mode by the UE based on the MICO mode indication from the UE, subscription information, and local policy of the AMF. In an example, the local policy may indicate that the MICO mode is not acceptable for UEs served by the AMF. In another example, the local policy may indicate that the MICO mode is not acceptable for UEs located in a specific area (e.g. a specific tracking area and/or a specific cell). In an example, if the MICO mode is acceptable for the UE, the AMF may include the MICO mode indication in a registration accept message and send the registration accept message to the UE. The AMF may indicate or mark the negotiation result (e.g., MICO is accepted or not for the UE) in UE context information at the AMF.

In an example, the base station may detect inactivity of the UE and determine a context release for the UE. In an example, the base station may start a UE context release procedure by sending a context release request message to the AMF. In an example, the base station may send an RRC release message to the UE in response to the UE context release procedure. In an example, the UE may enter CM-IDLE/RRC-IDLE state and activate the MICO mode in response to receiving the RRC release message. In an example, the AMF may activate the MICO mode for the UE in response to the CM state of the UE changing from CM-CONNECTED to CM-IDLE.

In an example, a UPF may receive a downlink data packet for the UE. The UPF may send a downlink data notification message to an SMF in response to the receiving the downlink data packet for the UE. In an example, the SMF may send a communication request message to the AMF in response to receiving the downlink data notification from the UPF, requesting a communication setup with the UE. The communication request message may be a Namf_Communication_N1N2MessageTransfer. In an example, the AMF may determine that the UE is unreachable during the duration of the MICO mode and the AMF may send a communication request response message comprising reject cause to the SMF. In an example, the communication request response message may be Namf_Communication_N1N2MessageTransfer Response message. In an example, the reject cause may indicate that the UE is in MICO mode. In an example, the SMF may send a failure indication to the UPF in response to receiving the communication request response message from the AMF with reject cause ‘UE is in MICO mode’. The failure indication may indicate the failure of downlink data transmission. In an example, the UPF may not send downlink data notification message to the SMF for the UE before receiving an explicit indication that the UE has deactivated MICO mode. In an example, the UE may deactivate the MICO mode based on the UE initiating an uplink data transfer or uplink signaling.

FIG. 18 illustrates an example call flow of a UE requesting to cancel/disable a previously accepted MICO mode with an AMF.

In an example, a UE may cancel/disable a previously accepted MICO mode with an AMF, such as the accepted MICO mode discussed above in regard to FIG. 17. The UE may send a registration request message without including an indication of MICO mode. The AMF may determine a cancellation/disabling of the MICO mode in response to receiving the registration request message from the UE. In an example, the AMF may respond by sending a registration accept message to the UE, without including MICO mode indication, in response to the determining. The AMF and the UE may set/mark that MICO mode is not used for the UE in response to this “re-negotiation” between the UE and the AMF. In an example, a base station may release UE context and send an RRC release message to the UE. In an example, the UE may enter CM-IDLE state in response to receiving the RRC release message. In an example, the UE does not activate the MICO mode and the UE may monitor paging and perform serving cell and neighbor cell monitoring for cell reselection. In an example, during the time the UE is in CM-IDLE state, the AMF may page the UE in response to the arrival of downlink data for the UE.

In an example, during a registration procedure, a UE may request an active time value from the AMF as part of MICO mode negotiation. In an example, the active time value may define a time duration or time window, referred to as the active time, that the UE is reachable for paging after a mobile initiated data transaction/transmission is completed and the UE has transitioned from a connected state to an idle state. In an example, a UE using MICO mode may send data to an application server and the UE may enter MICO mode after the completion of sending the data. In an example, the application server may send an acknowledgement message to the UE in response to receiving the data from the UE. In an example, the application server may be able to utilize the active time to send the acknowledgement data to the UE before the UE enters the MICO mode. More specifically, the application server may send the acknowledgement data to the UE during the active time before the UE enters the MICO mode.

In an example, the AMF may accept the MICO mode with an active time value in response to receiving a registration request message comprising the MICO mode indication and the active time value. The AMF may determine acceptance of the MICO mode, and the active time value based on local configuration, an expected UE behavior if available, the UE requested active time value, the UE subscription information, network policies, and/or the like. In an example, the AMF may assign the active time value to the UE and the AMF may consider the UE reachable for paging after the UE transitions from a connected state (e.g., CM-CONNECTED) to an idle state (e.g., CM-IDLE) for the duration of the active time.

If the AMF allocates an active time value to a UE, the registration area of the UE may be constrained by paging area size. In an example, the AMF may allocate the active time value to the UE and the AMF may not allocate ‘all PLMN’ registration area to the UE to avoid paging in the entire PLMN.

The UE may set a timer corresponding to the active time value negotiated during the most recent registration procedure. In an example, the UE may start the timer in response to entering CM-IDLE state from CM-CONNECTED state. In an example, the UE enters/activates MICO mode in response to expiration of the timer. In an example, the expiration of the timer may be that the timer reaches the active time value. In an example, the UE may stop and reset the timer in response to entering CM-CONNECTED state before the timer expires.

If no active time value was assigned by the AMF during MICO negotiation the UE may not start the timer and may instead enter MICO mode directly upon entering CM-IDLE state.

FIG. 19 illustrates an example call flow of the MICO mode operation with an active time. In an example, a UE may send a registration request message to an AMF requesting MICO mode negotiation with an active time value. In an example, the registration request message may comprise a MICO mode preference, a MICO mode indication, an active time value, and/or the like. The AMF may accept the MICO mode and use of the active time and may send a registration accept message in response to receiving the registration request message. In an example, the registration accept message may comprise a MICO mode indication and an active time value. The active time value provided by the AMF may be same as the active time value provided by the UE during registration procedure. In an example, the base station may send an RRC release message in response to determining UE inactivity for a period of time (e.g. there is no transmission from or reception by the UE in 10 seconds). In an example, the UE may enter CM-IDLE state in response to receiving an RRC release message from a base station. The UE and the AMF may start an active timer in response to entering/transitioning to CM-IDLE state. In an example, the UE may monitor for paging messages from the network during a time duration that the timer is running. In an example, the timer may be expired if the timer reaches the active time value. In an example, the UE may activate MICO mode in response to expiration of the active timer. The UE may switch off access stratum of the UE while the MICO mode is activated. In an example, the UE may deactivate the MICO mode based on the UE initiating an uplink data transfer or uplink signaling.

A UE may use an active time, as explained above, before the UE enters MICO mode. In existing wireless technologies, the UE in the active time may need to establish a new RRC connection in response to receive a paging message for a mobile terminated service. The establishment of a new RRC connection may require more RRC messages than resuming an existing RRC connection (e.g., nine RRC messages for establishment of a new RRC connection versus six or seven RRC messages for resuming an existing RRC connection) and may result in additional power consumption on the UE side. For a UE, which may be a battery constrained device, MICO mode with low power consumption demands is needed.

In an example embodiment, an AMF may determine whether to use a MICO mode with RRC inactive state. If the AMF determines to use MICO mode with RRC inactive, the AMF may provide corresponding information to a serving base station during a connection setup procedure for a UE. The base station may derive an active time value and provide the active time value to the UE during an RRC suspension procedure. If the wireless device receives a paging message after entering/transitioning to RRC inactive state but before the UE enters/activates the MICO mode (or, in other words, before expiration of an active timer determined based on the active time value), the UE may request resumption of the existing RRC connection instead of establishment of a new RRC connection. In an example embodiment, the base station and the UE may maintain an RRC timer to control the active time and the activation of MICO mode. If the RRC timer expires in the UE, the UE may enter/transition to RRC idle state without an explicit signaling exchange with the base station. If the timer expires in the base station, the base station may indicate to the AMF that the UE enters the MICO mode. Embodiments of the present disclosure may increase battery power efficiency of the UE by reducing the number of transitions of the RRC signaling.

FIG. 20 illustrates an example embodiment for MICO mode usage with RRC inactive state in accordance with the present disclosure. As shown in FIG. 20, a UE may negotiate a MICO mode usage with an AMF during a registration procedure. In an example, the MICO mode usage may be whether a MICO mode is acceptable or not for the UE. In an example, the MICO mode usage may be whether an active time value with the MICO mode is assigned or not. In an example, the UE may send a registration request message, via a base station to the AMF, requesting the MICO mode usage. In an example, the registration message may comprise a registration type, a UE identity (e.g., SUCI, 5G-GUTI), the location of the UE (e.g., last visited TAI), requested NSSAI, UE mobility management context information, PDU session state, information for the MICO mode usage, and/or the like. In an example, the information of the MICO mode usage may comprise a MICO mode indication, an active time value, latency information, and/or the like. In an example, the MICO mode indication may indicate a preference, capability, and/or the like of the UE to employ the MICO mode. In an example, the active time value (e.g. 30 seconds) may indicate the time period after entering/transitioning to RRC inactive that the UE wants/prefers to be reachable by paging message before entering the MICO mode. In an example, the latency information (e.g. 30 minutes) may indicate a tolerant communication latency with an application sever of the UE (e.g. delay tolerant, and/or the like).

In an example, the AMF may determine whether to accept the MICO mode usage in response to receiving the registration request message. In an example, the AMF may determine whether to accept the MICO mode and a period of the active time value (e.g. 0-s, 10-s, 1-minute) for the UE. In an example, the determination may be based on local configuration, an expected UE behavior, the UE requested active time value, the UE subscription information, network policies, and/or the like. In an example, the expected UE behavior may be a set of parameters provisioned by an external party to 5G network functions via a NEF on the foreseen or expected UE behavior. In an example, the provisioned expected UE behavior parameters may be used for the setting of mobility management or session management parameters of the UE. In an example, the expected UE behavior may indicate that the UE is a stationary or low mobility UE. In an example, the AMF may send the accepted MICO mode usage by sending a registration accept message to the UE. In an example, the registration accept message may comprise 5G-GUTI, registration area, a periodic registration area update time value, a MICO mode indication, an active time value, and/or the like.

In an example, the AMF may determine whether to use a MICO mode with RRC inactive. In an example, the AMF may determine to use the MICO mode with RRC inactive for a UE requiring further power saving. In an example, the AMF may determine to use MICO mode and an active time with RRC inactive state based on the expected UE behavior or a communication pattern of the application. In an example, the communication pattern may indicate a schedule of data transmission (e.g., downlink data transmission is planned within 30 seconds after completion of mobile originated data transmission) for the UE with an application server.

In an example, the AMF may send a context setup request message to a base station in response to the determination (e.g., using MICO mode and an active time with RRC inactive). In an example, the context setup request message may be an initial context setup request message. In an example, the context setup request message may be a UE context modification request message. In an example, the context setup request message may comprise a parameter indicating MICO mode is allowed/accepted for the UE, an active time value, AMF UE NGAP ID, RAN UE NGAP ID, old AMF address, UE aggregate maximum bit rate, PDU session information for setup, and/or the like. In an example, the AMF UE NGAP ID may uniquely identify a UE association over the NG interface (e.g. N2 interface) within the AMF side. The RAN UE NGAP ID may uniquely identify a UE association over the NG interface within the NG-RAN side. In an example, the base station may send a context setup response message in response to receiving the context setup request message from the AMF. In an example, the context setup response message may be an initial context setup response. In an example, the context setup response message may be a UE context modification response message. In an example, the context setup response message may comprise an indication that the MICO mode usage is accepted by the base station, AMF UE NGAP ID, RAN UE NGAP ID, PDU session resource setup response list, PDU session resource failed to setup list and/or the like.

In an example, the base station may detect an inactivity of the UE and determine to suspend an RRC connection with the UE. In an example, the base station may send an RRC release message to the UE in response to the determination. In an example, the RRC release message may comprise suspension/suspend configuration information, an active time value (e.g. an active time value for RRC inactive), an MICO indication, and/or the like.

In an example, the suspension/suspend configuration information may comprise a radio network temporary identity (RNTI), a radio access network (RAN) paging cycle, a RAN notification area (RNA) information, a periodic RNA update time value, and/or the like. In an example, the active time value may be same value with the active time value negotiated between the UE and the AMF. In an example, the active time value may be smaller than the periodic RNA update time value. In an example, the periodic RNA update time value may be 10 minutes and the active time value may be 1 minute. In an example, the RAN notification area information may comprise a list of cells, a PLMN identity, a list of tracking area codes, a list of RAN area code, and/or the like. In an example, the UE may perform a RAN notification area update procedure in response to entering a cell which does not belong to the RNA. In an example, the UE may perform the RAN notification area update procedure in response to entering a new RNA. In an example, the base station may determine the periodic RNA update time value based on the periodic registration area update time value. In an example, the periodic RNA update time value (e.g., 30 minutes or 1 hour) may be smaller than the periodic registration area update time value (e.g., 3 hours or 12 hours).

In an example, the UE may transition/enter the RRC inactive state from the RRC connected state in response to receiving the RRC release message comprising the suspension configuration information. In an example, the UE may start an RRC timer in response to transitioning from the RRC state to the RRC inactive if the UE receives the active time value.

In an example, the RRC state of the UE in the base station may change from RRC connected to RRC inactive in response to sending the RRC release message to the UE. In an example, the base station may start an RRC timer for the UE based on the active time value. In an example, the RRC timer of the UE and the base station may expire in response to reaching to the active time value. In an example, the active time value (e.g. active time value for the RRC inactive state) may be 1 minute and the RRC timer expires if the RRC timer reaches 1 minute. In an example, the time duration that the RRC timer is running is an active time. In an example, the UE may monitor for paging messages during the active time. In an example, the base station may page the UE during the active time in response to receiving a data packet or signaling message from the AMF or the UPF. In an example, during the active time, the UE may send an RRC resume request message to the base station if the UE initiates uplink data transfer or signaling. In an example, the UE may send an RRC resume request message during the active time, in response to receiving a paging message from the base station.

In an example, during the active time, the UE may send an RRC resume request message to perform a RAN notification area update procedure in response to entering a new RNA (e.g., the area/cell does not belong to the current RNA). In an example, the UE may stop and reset the RRC timer in response to performing the RAN notification area update procedure.

In an example, the UE may activate/enter the MICO mode and transition/enter to CM-IDLE/RRC idle state from the CM-CONNECTED/RRC inactive state, in response to the expiration of the RRC timer of the UE. In an example, the base station may send a context release request message to the AMF, indicating that the UE enters MICO mode, in response to the expiration of the RRC timer of the base station. In an example, the AMF may respond to the base station, a release of N2, N3 connection with the UE, in response to receiving the context release request message. In an example, the base station may delete/remove context information of the UE in response to completing the context release procedure. In an example, the context information of the UE may comprise a UE identity (RNTI, temporary UE identity), a RAN notification area information, a periodic RAN notification area update timer, tunnel information for the UE, and/or the like. In an example, the AMF may indicate/mark that the UE activates/enters the MICO mode in response to receiving the indication that the UE activates/enters MICO mode from the base station. In an example, the AMF may reject incoming communication request message from network functions (e.g. SMF, NEF, UDM) in response to the UE entering/activating the MICO mode.

In an example, the UE may deactivate the MICO mode and may send an RRC setup request message if the UE initiates uplink data transfer or signaling. In an example, the UE may switch on access stratum and start cell searching to camp on a proper cell in response to deactivating the MICO mode.

FIG. 23 is a flow diagram as per an aspect of an example embodiment of the present disclosure. A UE may be in CM-CONNECTED/RRC connected state. The UE may receive an RRC release message from a base station. The RRC message may comprise parameters for RRC suspension configuration. The wireless device may transition/enter an CM-IDLE/RRC idle state if the RRC release message does not comprise the parameters for the RRC suspension configuration. The wireless device may transition to an CM-CONNECTED/RRC inactive state if the RRC release message comprise the parameters for the RRC suspension configuration. In an example, the RRC release message may further comprise a timer value indicating an active time period for the RRC inactive state. If the RRC message further comprises the timer value, the wireless device may set an RRC timer based on the timer value and may start the RRC timer. If the RRC message does not comprise the timer value, the wireless device stays the CM-CONNECTED/RRC inactive state. In an example, the RRC timer may be expired. If the RRC timer is expired, the wireless device may transition to CM-IDLE/RRC idle state. Based on the RRC timer expiration, the wireless device may active a MICO mode. The wireless device may delete context for RRC connections based on the RRC timer expiration. The wireless device may not perform a cell reselection procedure based on the RRC timer expiration. The wireless device may switch off an access stratum of the UE.

FIG. 24 is a flow diagram as per an aspect of an example embodiment of the present disclosure. In an example, a UE may be in an CM-IDLE/RRC idle state. The UE may want to send data/signaling before the expiration of the RRC timer. The UE may need to send data/signaling before the expiration of the RRC timer. If the UE needs to send data/signaling before the expiration of the RRC timer, the UE may start cell searching procedure to camp on a suitable cell and the UE may read system information of the suitable cell. If the UE camps on a cell which is not in a registration area or triggering of this procedure is in response to expiration of periodic registration area update timer, a non-access stratum (NAS) layer of the UE may send a registration update message to an access stratum (AS) layer of the UE. The AS layer of the UE may send an RRC setup request message indicating an establishment cause as signaling. If the UE camps on a cell which is in a registration area or triggering of this procedure is other than due to expiration of periodic registration area update timer, a non-access stratum (NAS) layer of the UE may send a service request message to an access stratum (AS) layer of the UE. The AS layer of the UE may send an RRC setup request message indicating an establishment cause as data. After RRC connection establishment, the UE may send a NAS message (the service request message or the registration update message) of the wireless may send to the AMF.

FIG. 25 is a flow diagram as per an aspect of an example embodiment of the present disclosure. In an example, an AMF may negotiate a MICO mode with a UE via a registration procedure. The AMF and the UE may store same active time period for an CM-IDLE/RRC idle state. The AMF may determine to apply the active time period for a MICO mode with an RRC idle state. If the AMF determines to apply the active time period for the MICO mode with an RRC idle state, the AMF may send a context setup request message, to a base station. The context setup request message may comprise an active time period for an RRC inactive state, a parameter indicating that a MICO mode is allowed for the UE. The active time period for the RRC inactive state may be based on the active time period for the CM-IDLE/RRC idle state. The AMF may determine the active time period for the RRC inactive state based on the active time period for the CM-IDLE/RRC idle state. In an example, the AMF may receive a context release message, from the base station, indicating that the UE activates the MICO mode. If the AMF receives the context release message indicating that the UE activates the MICO mode, the AMF may mark/store that the UE activated the MICO mode to UE context in the AMF. If the AMF receives any terminated call for a UE marked as activating the MICO mode, the AMF may reject the terminated call by sending a cause indicating that terminated services are not available for the UE. The AMF may start a periodic registration update time in response to receiving the context release message indicating that the UE activates the MICO mode.

At FIG. 25, in an example, The AMF may determine do not apply the active time period for the MICO mode with the RRC inactive state. Instead, the AMF may determine to apply the active time period for the MICO mode with the CM-IDLE/RRC idle state. If the AMF determine to apply the active time period for the MICO mode with the CM-IDLE/RRC idle state, the AMF may a NAS timer based on the active time period for the CM-IDLE/RRC idle state in response to the UE entering an CM-IDLE/RRC idle state. If the NAS time expires, the AMF may mark/store that the UE activated the MICO mode to UE context in the AMF. If the AMF receives any terminated call for a UE marked as activating the MICO mode, the AMF may reject the terminated call by sending a cause indicating that terminated services are not available for the UE. The AMF may start a periodic registration update time based on the entering the CM-IDLE/RRC idle state.

FIG. 21 illustrates an example call flow for MICO mode usage with RRC inactive state in accordance with embodiments of the present disclosure. As shown in FIG. 21, a UE may negotiate a MICO mode usage with an AMF during a registration procedure. In an example, the MICO mode usage may be whether a MICO mode is acceptable or not for the UE. In an example, the MICO mode usage may be whether an active time value with the MICO mode is assigned or not. In an example, the UE may send a registration request message via a base station to the AMF, requesting the MICO mode usage. In an example, the registration message may comprise a registration type, a UE identity (e.g. SUCI, 5G-GUTI), the location of the UE (e.g. last visited TAI), requested NSSAI, UE mobility management context information, PDU session state, information for the MICO mode usage, and/or the time. In an example, the information of the MICO mode usage may comprise MICO mode indication, an active time value, latency information, and/or the like. In an example, the MICO mode indication may indicate that the UE wants/prefers use of MICO mode. In an example, the active time value (e.g. 30 seconds) may indicate the time period after entering/transitioning to RRC inactive that the UE wants/prefers to be reachable by paging message before entering the MICO mode. In an example, the latency information (e.g. 30 minutes) may indicate a tolerant communication latency with an application sever of the UE.

In an example, the AMF may determine whether to accept the MICO mode usage in response to receiving the registration request message. In an example, the AMF may determine whether to accept the MICO mode and a period of the active time value (e.g. 0-s, 10-s, 1-minute) for the UE. In an example, the determination may be based on local configuration, an expected UE behavior, the UE requested active time value, the UE subscription information, network policies, and/or the like. In an example, the expected UE behavior may be a set of parameters provisioned by an external party to 5G network functions via NEF on the foreseen or expected UE behavior. In an example, the provisioned expected UE behavior parameters may be used for the setting of mobility management or session management parameters of the UE. In an example, the expected UE behavior may indicate that the UE is stationary or low mobility UE. In an example, the AMF may send the accepted MICO mode usage by sending registration accept message to the UE. In an example, the registration accept message may comprise 5G-GUTI, registration area, a periodic registration area update time value, a MICO mode indication, an active time value and/or the like.

In an example, the AMF may determine whether to use a MICO mode with RRC inactive. In an example, the AMF may determine to use MICO mode with RRC inactive for a UE requiring further power saving. In an example, the AMF may determine to use MICO mode and an active time with RRC inactive based on the expected UE behavior or a communication pattern of the application. In an example, the communication pattern may indicate a schedule of data transmission (e.g. downlink data transmission is planned within 30 seconds after completion of mobile originated data transmission) for the UE with an application server.

In an example, the AMF may send a context setup request message to a base station in response to the determination (e.g., applying MICO mode with RRC inactive). In an example, the context setup request message may be an initial context setup request message. In an example, the context setup request message may be a UE context modification request message. In an example, the context setup request message may comprise a parameter indicating the MICO mode is allowed for the UE, an active time value, AMF UE NGAP ID, RAN UE NGAP ID, old AMF address, UE aggregate maximum bit rate, PDU session information for setup and/or the like. In an example, the AMF UE NGAP ID may uniquely identify a UE association over the NG interface (e.g. N2 interface) within the AMF side. The RAN UE NGAP ID may uniquely identify a UE association over the NG interface within the NG-RAN side. In an example, the base station may response to the AMF by sending a context setup response message, in response to receiving the context setup request message from the AMF. In an example, the context setup response message may be an initial context setup response. In an example, the context setup response message may be a UE context modification response message. In an example, the context setup response message may comprise an indication that the MICO mode usage is accepted by the base station, AMF UE NGAP ID, RAN UE NGAP ID, PDU session resource setup response list, PDU session resource failed to setup list and/or the like.

In an example, the base station may detect an inactivity of the UE and determine to suspend an RRC connection with the UE. In an example, the base station may send RRC release message to the UE in response to the determination. In an example, the RRC release message may comprise suspension/suspend configuration information, an active time value for RRC inactive, the MICO indication and/or the like.

In an example, the suspension/suspend configuration information may comprise a radio network temporary identity (RNTI), a radio access network (RAN) paging cycle, a RAN notification area (RNA) information, a periodic RNA update time value and/or the like. In an example, the active time value for RRC inactive may be same with the active time value for RRC idle. In an example, the active time value for RRC inactive may be smaller than the periodic RNA update time value. In an example, the periodic RNA update time value may be 10 minutes and the active time value for RRC inactive may be 1 minute. In an example, the RAN notification area information may comprise a list of cells, a public land mobile network (PLMN) identity, a list of tracking area codes, a list of RAN area code and/or the like. In an example, the UE may perform RAN notification area update procedure in response to entering a cell which does not belong to the RNA. In an example, the UE may perform RAN notification area update procedure in response to entering new RNA. In an example, the base station may determine the periodic RNA update time value based on the periodic registration area update time value. In an example, the periodic RNA update time value (e.g. 30 minutes or 1 hour) may be smaller than the periodic registration area update time value (e.g. 3 hours or 12 hours).

In an example, the UE may transition/enter to the RRC inactive state from the RRC connected state in response to receiving the RRC release message comprising the suspension configuration information. In an example, the UE may start an RRC timer in response to entering/transitioning the RRC state to the RRC inactive state if the UE receives the active time value.

In an example, the RRC state of the UE in the base station may change from the RRC connected state to the RRC inactive state in response to sending the RRC release message to the UE. In an example, the base station may start an RRC timer of the UE based on the active time value for the RRC inactive state. In an example, the RRC timer of the UE and the base station may be expired in response to reaching to the active time value for the RRC inactive. In an example the active time value for the RRC inactive may be 1 minute and the RRC timer expires if the RRC timer reaches 1 minute. In an example, the time duration that the RRC timer is running is an active time. In an example, the UE may monitor paging message during active time. In an example, the base station may page the UE during the active timer period in response to receiving a data packet or signaling message from the AMF or the UPF. In an example, during the active time, the UE may send an RRC resume request message to the base station if the UE initiates uplink data transfer or signaling. In an example, the UE may send an RRC resume request message during the active time, in response to receiving paging message from the base station.

In an example, the UE may activate/enter the MICO mode and stay in the CM-CONNECTED/RRC inactive state, in response to the expiration of the RRC timer of the UE. In an example, the base station may indicate to the AMF that the UE enters MICO mode, in response to the expiration of the RRC timer of the base station. In an example, the AMF may indicate/mark that the UE activates/enters the MICO mode in response to receiving the indication that the UE activates/enters MICO mode from the base station. In an example, the AMF may reject incoming communication request message from network functions (e.g. SMF, NEF, UDM) in response to the UE entering/activating the MICO mode.

In an example, the UE may deactivate the MICO mode and send an RRC resume request message if the UE initiates uplink data transfer or signaling. The UE may switch on access stratum and start cell searching to camp on a proper cell in response to deactivating the MICO mode.

FIG. 26 is a flow diagram as per an aspect of an example embodiment of the present disclosure. A UE may be in CM-CONNECTED/RRC connected state. The UE may receive an RRC release message from a base station. The RRC message may comprise parameters for RRC suspension configuration. The wireless device may transition/enter an CM-IDLE/RRC idle state if the RRC release message does not comprise the parameters for the RRC suspension configuration. The wireless device may transition to an CM-CONNECTED/RRC inactive state if the RRC release message comprise the parameters for the RRC suspension configuration. In an example, the RRC release message may further comprise a timer value indicating an active time period for the RRC inactive state. If the RRC message further comprises the timer value, the wireless device may set an RRC timer based on the timer value and may start the RRC timer. If the RRC message does not comprise the timer value, the wireless device stays the CM-CONNECTED/RRC inactive state. In an example, the RRC timer may be expired. If the RRC timer is expired, the wireless device may stay in the CM-CONNECTED/RRC inactive state. Based on the RRC timer expiration, the wireless device may active a MICO mode. The wireless device may not perform a cell reselection procedure based on the RRC timer expiration. In an example, the wireless device may switch off an access stratum of the UE.

FIG. 27 is a flow diagram as per an aspect of an example embodiment of the present disclosure. In an example, a UE may be in CM-CONNECTED/RRC Inactive state and may activate a MICO mode. The UE may need to send data/signaling. If the UE wants/needs to send data/signaling, the UE may deactivate the MICO mode and switch on an access stratum (AS) of the UE. If the UE needs to send data/signaling, the UE may start cell searching procedure to camp on a suitable cell and the UE may read system information of the suitable cell. If the UE camps on a cell which is not in a RAN notification area or triggering of this procedure is other than an expiration of a RAN notification are update timer, the UE may send an RRC resume request message indicating an establishment cause as ‘mobile originated signaling or data’. If a triggering of the sending data/signaling is based on an expiration of a RAN notification area update timer, the UE may send an RRC resume request message indicating an establishment cause as ‘Periodic RAN notification area update”.

FIG. 22 illustrates an example call flow for MICO mode usage with RRC idle in accordance with embodiments of the present disclosure. As shown in FIG. 22, a UE may negotiate a MICO mode usage with an AMF during a registration procedure. In an example, the MICO mode usage may be whether a MICO mode is acceptable or not f According to various embodiments, a device such as, for example, a wireless device, a device, a base station, and/or the like, may comprise one or more processors and memory. The memory may store instructions that, when executed by the one or more processors, cause the device to perform a series of actions. or the UE. In an example, the MICO mode usage may be whether an active time value with the MICO mode is assigned or not. In an example, the UE may send a registration request message via a base station to the AMF, requesting the MICO mode usage. In an example, the registration message may comprise a registration type, a UE identity (e.g. SUCI, 5G-GUTI), the location of the UE (e.g. last visited TAI), requested NSSAI, UE mobility management context information, PDU session state, information for the MICO mode usage and/or the time. In an example, the information of the MICO mode usage may comprise MICO mode indication, an active time value, latency information and/or the like. In an example, the MICO mode indication may indicate that the UE wants/prefers use of MICO mode. In an example, the active time value (e.g. 30 seconds) may indicate the time period after entering/transitioning to RRC inactive that the UE wants/prefers to be reachable by paging message before entering the MICO mode. In an example, the latency information (e.g. 30 minutes) may indicate a tolerant communication latency with an application sever of the UE.

In an example, the AMF may determine whether to accept the MICO mode usage in response to receiving the registration request message. In an example, the AMF may determine whether to accept the MICO mode and a period of the active time value (e.g. 0-s, 10-s, 1-minute) for the UE. In an example, the determination may be based on local configuration, an expected UE behavior, the UE requested active time value, the UE subscription information, network policies, and/or the like. In an example, the UE behavior may a set of parameters provisioned by an external party to 5G network functions via NEF on the foreseen or expected UE behavior. In an example, the provisioned expected UE behavior parameters may be used for the setting of mobility management or session management parameters of the UE. In an example, the expected UE behavior may indicate that the UE is stationary or low mobility UE. In an example, the AMF may send the accepted MICO mode usage by sending registration accept message to the UE. In an example, the registration accept message may comprise 5G-GUTI, registration area, a periodic registration area update time value, a MICO mode indication, an active time value, and/or the like.

In an example, the AMF may send a context setup request message to provide connection management assistance information with the UE. In an example, the connection management assistance information may comprise an RRC inactive assistance information and an immediate release indication. In an example, the immediate release indication may indicate a release of RRC connection with the UE after completion of data transmission/reception with the UE. In an example, the AMF may include the immediate release indication when the AMF determine MICO mode usage with RRC idle state for the UE. In an example, the AMF may include the immediate release indication in the context setup request message to indicate that the base station does not keep the UE in RRC inactive state after the data transmission completed. In an example, the base station may perform a connection release procedure with the AMF and an RRC connection release procedure with a UE, in response to detection of UE inactivity and if the base station receives the immediate release indication in context setup request message. In an example, the base station may perform a context release procedure with the AMF instead of keeping the UE in CM-CONNECTED state in response to the UE inactivity detection. In an example, the base station may send an RRC release message without including suspension/suspend configuration to the UE, requesting release of the RRC connection.

In an example, the UE may enter/transition to CM-IDLE/RRC-IDLE state in response to receiving the RRC release message. In an example, the access stratum (AS) layer of the UE may indicate to a non-access stratum (NAS) layer of the UE, the UE entering CM-IDLE/RRC-IDLE state. In an example, the NAS layer of the UE may start a NAS timer in response to transitioning/entering CM-IDLE/RRC-IDLE state. In an example, the UE may monitor paging message during a time duration that the NAS timer is running. In an example, the NAS timer may expire if the NAS timer reaches the active time value. In an example, the UE activate the MICO mode in response to the expiration of the NAS timer. The AMF may start a NAS timer in response to completion the context release procedure.

In an example, an RRC inactive state may be named as an RRC-INACTIVE or an RRC-inactive state. In an example, an RRC idle state may be named as an RRC-IDLE or an RRC-idle. In an example, an RRC connected may be named as an RRC-CONNECTED or an RRC-connected.

In an example, a CM idle state may be named as a CM-IDLE or a CM-idle. In an example, a CM connected may be named as a CM-CONNECTED or a CM-connected.

In an example, the UE may receive from a base station, a radio resource control (RRC) message to transition the UE from an RRC connected state to an RRC inactive state. The RRC message may comprise parameters for RRC suspension and a time value indicating an active time period for the RRC inactive state.

In an example, the UE may start a timer based on the active time period for the RRC inactive state, in response to receiving the RRC message (e.g., in response to transitioning to the RRC inactive state). In an example, the UE may determine expiration of the timer. In an example, the UE may activate a mobile initiated communication only (MICO) mode and transition into an RRC idle state from the RRC inactive state in response to the determining.

In an example, the RRC suspension may comprise the transitioning the UE from the RRC connected state to the RRC inactive state.

In an example, the parameters for the RRC suspension may comprise a radio network temporary identity (RNTI), a radio access network (RAN) paging cycle, a RAN notification area (RNA) information, a periodic RNA update time value, and/or the like.

In an example, the time value indicating the active time period for the RRC inactive state may be smaller than the periodic RNA update time value.

In an example, the RNA information may comprise at least one of a list of cells, a public land mobile network (PLMN) identity, a list of tracking area codes, a list of RAN area code, and/or the like.

In an example, the UE may send a registration request message to an access and mobility management function (AMF) via the base station. The registration request message may comprise information for the MICO mode. In an example, the information for the MICO mode may comprise an information element indicating MICO mode, a latency information for communication, a type of registration request, and/or the like.

In an example, the MICO mode may indicate whether the UE prefers/needs/requires the MICO mode. In an example, the type of registration may comprise at least one of an initial registration, a mobility registration updating, periodic registration updating, emergency registration, and/or the like.

In an example, the UE may receive, a registration accept message from the AMF via the base station, to confirm a successful registration with the AMF. In an example, the registration accept message may comprise a registration area, a parameter indicating the MICO mode is allowed for the wireless device, a periodic registration area update time value, an active time period for an RRC idle state, and/or the like.

In an example, the time value indicating the active time period for the RRC inactive state may be smaller than the periodic registration area update time value.

In an example, the UE may start a second timer based on the periodic registration area update time value for a registration procedure.

In an example, by an access stratum (AS) layer of the UE may indicate activating the MICO mode of the UE to a non-access stratum (NAS) layer of the UE, in response to the expiration of the timer.

In an example, the UE may stop the timer and transition from the RRC inactive state to the RRC connected state, in response to performing a radio access network notification area (RNA) update procedure.

In an example, the RNA update procedure may be in response to the UE entering a second RNA different from the RNA.

In an example, the UE may send an RRC resume request message (to the base station) to establish an RRC connection during a time duration that the timer is running.

In an example, the UE may send an RRC setup request message (to the base station) to establish an RRC connection after (e.g., based on) the expiration of the timer.

In an example, the UE may switch off an access stratum (AS) in response to the activating the MICO mode.

In an example, the AS may comprise a transmitter of the wireless device, a receiver of the wireless device, a baseband of the wireless device, and/or the like.

In an example, the UE may monitor a RAN paging during a time duration that the timer is running.

In an example, the base station may perform a paging procedure for the UE in response to receiving/arriving a packet data or a signaling data for the wireless device and the timer is running.

In an example, the UE may deactivate the MICO mode, to send data/signaling.

In an example, a UE may receive a radio resource control (RRC) message from a base station, to transition the wireless device from an RRC connected state to an RRC inactive state. In an example, the RRC message may comprise parameters for RRC suspension and a time value indicating an active time period for the RRC inactive state, and/or the like. In an example, the UE may start a timer based on the active time period for the RRC inactive state, in response to receiving the RRC message (e.g., in response to transitioning to the RRC inactive state), a timer based on the active time period for the RRC inactive state.

In an example, the UE may determine expiration of the timer. In an example, the UE may active a mobile initiated communication only (MICO) mode, in response to the determining.

In an example, the may transition from the RRC inactive state to and RRC idle state, in response to the activating the MICO mode.

In an example, a UE may receive a radio resource control (RRC) message from a base station to transition the UE from an RRC connected state to an RRC inactive state. In an example, the RRC message may comprise parameters for RRC suspension, an active time period for RRC inactive and/or the like.

In an example, the UE may start a timer based on the active time period for RRC inactive, in response to receiving the RRC message. In an example, the UE may perform an RRC resume in response to receiving RAN paging message during the active time period.

In an example, the UE may determine, the timer is expired. In an example, the UE may activate a mobile initiated mode only (MICO) mode, in response to the determining.

In an example, the UE may send (to the base station), an RRC resume request message requesting an RRC connection setup and deactivating the MICO mode.

In an example, the UE may stay in the RRC inactive state after activating the MICO mode.

In an example, a base station may receive a context setup request message from an access and mobility management function (AMF), a context setup request message requesting a connection establishment for a UE. In an example, the context setup request message may comprise core network assistance information, an indication that a mobile initiated communication only (MICO) mode is allowed for the wireless device, an active time period for the MICO mode, and/or the like.

In an example, the base station may send to the AMF, a context setup response message indicating completion of the connection establishment for the UE.

In an example, the base station may detect, a user inactivity of the wireless device. The base station may determine to apply/use the MICO mode with a radio resource control (RRC) inactive state for the UE. In an example, the base station may send to the UE, in response to the detecting, an RRC message to transition the wireless device from an RRC connected state to the RRC inactive state. In an example, the RRC message may comprise parameters for RRC suspension, an active time period for RRC inactive (the active time period for RRC inactive is based on the active time period for MICO mode).

In an example, the base station may start a timer based on the active time period for the RRC inactive, in response to sending the RRC message. The base station may detect expiration of the timer. In an example, the base station may send to the AMF, at least one context release request message requesting connection release for the UE in response to the detecting. In an example, the at least one context release request message may indicate that the UE activates the MICO mode.

In an example, the base station may delete a context of the UE in response to the detecting.

In an example, the base station may perform a radio access network (RAN) paging procedure during a time duration that the timer is running.

In an example, a base station may receive from an access and mobility management function (AMF), a context setup request message requesting a connection establishment for a UE. In an example, the context setup request message may comprise core network assistance information, an indication that a mobile initiated communication only (MICO) mode is allowed for the wireless device, an active time period for the MICO mode.

In an example, the base station may send to the AMF, a context setup response message indicating completion of the connection establishment for the UE.

In an example, the base station may detect a user inactivity of the UE. The base station may determine to apply/use the MICO mode with a radio resource control (RRC) inactive state for the UE. In an example, the base station may send to the UE, in response to the detecting, an RRC message to transition the UE from an RRC connected state to the RRC inactive state.

In an example, the RRC message comprising parameters for RRC suspension, an active time period for RRC inactive (wherein the active time period for RRC inactive is based on the active time period for MICO mode), and/or the like.

In an example, the base station may start a timer based on the active time period for the RRC inactive, in response to sending the RRC message. In an example, the base station may detect expiration of the timer.

In an example, the base station may send to the AMF, in response to the detecting, at least one context release request message requesting connection release for the UE. In an example, the at least one context release request message may indicate that the UE activates the MICO mode.

In an example, an access and mobility management function (AMF) may receive from a UE via a base station, a registration request message requesting a registration of the wireless device. In an example, the registration request message may comprise an indication mobile initiated only communication (MICO) mode, a latency information for communication, a type of registration request, and/or the like.

In an example, the AMF may send to the UE via the base station, a registration accept message to confirm a successful registration with the AMF for the UE. In an example, the registration accept message may comprise a registration area, a parameter indicating the MICO mode is allowed for the wireless device, a periodic registration area update time value, an active time period for radio resource control (RRC) idle, and/or the like.

In an example, the AMF may determine using/applying a MICO mode with RRC inactive. The AMF may send to the base station and in response to the determining, a context setup request message requesting a connection establishment for the UE. In an example, the context setup request message may comprise, a registration area of the wireless device, a parameter indicating the MICO mode is allowed for the wireless device, a periodic registration area update time value, an active time period for RRC inactive, UE specific DRX values and/or the like.

In an example, the AMF may receive from the base station, at least one context release request message requesting a context release/connection RRC release for the UE. In an example, the at least one context release request message may indicate that the UE activates the MICO mode.

In an example, the AMF may start a timer based on the periodic registration area update time value, in response to receiving the context release request message.

In an example, the determining is based on at least one of a communication pattern of the wireless device, the indication MICO mode, a local policy, and/or the like.

In an example, the active time period for RRC inactive is the active time period for RRC idle.

FIG. 28 is a flow diagram as per an aspect of an example embodiment of the present disclosure. At 2810, a wireless device may receive from a base station, a radio resource control (RRC) message to transition the wireless device from an RRC connected state to an RRC inactive state. The RRC message may indicate an active time period in which the wireless device is reachable by paging. At 2820, the wireless device may transition from the RRC connected state to the RRC inactive state in response to the RRC message. At 2830, the wireless device may monitor one or more paging messages during the active time period after the transitioning. At 2840, in response to an expiration of the active time period, the wireless device may activate a mobile initiated communication only (MICO) mode and may stop monitoring to receive the one or more paging messages.

In an example embodiment, a wireless device may receive from a base station, a radio resource control (RRC) message to transition the wireless device from an RRC connected state to an RRC inactive state, and the wireless device may be reachable by paging. The wireless device may transition from the RRC connected state to an RRC inactive state in response to the RRC message. The wireless device may monitor to receive a paging message during the active time period after the transitioning. In response to an expiration of the active time period, the wireless device may activate a mobile initiated communication only (MICO) mode and the wireless device may stop monitoring to receive the paging message. In an example, the wireless device may send, to the base station, an RRC resume request message to establish an RRC connection for mobile originated data transmission during the active time period. The wireless device may send, to the base station, the RRC resume request message to establish an RRC connection to respond to a paging message during the active time period. In an example, the wireless device may stay in the RRC inactive state based on the activating the MICO mode. The wireless device may send, to the base station, an RRC resume request message to establish an RRC connection for mobile originated data transmission based on the activating the MICO mode. In an example, the wireless device may transition to an RRC idle state based on the activating the MICO mode. The wireless device may send, to the base station, an RRC setup request message to establish an RRC connection for a mobile originated data transmission based on the activating the MICO mode. The wireless device may send to an access and mobility management function (AMF) a registration request message indicating that the wireless device prefers the MICO mode. The RRC message may comprises parameters for RRC suspension, and the parameters may comprise a radio network temporary identity (RNTI), a radio access network (RAN) paging cycle, a RAN notification area (RNA) indication, and a periodic RNA update time value. The active time period may be smaller than the periodic RNA update time value.

FIG. 29 is a flow diagram as per an aspect of an example embodiment of the present disclosure. At 2910, a base station may determine to release an RRC connection with a wireless device. At 2920, the base station may send, to the wireless device, an RRC message to transition the wireless device from an RRC connected state to an RRC inactive state. The RRC message may indicate an active time period in which the wireless device is reachable by paging.

In an example, a base station may determine to release an RRC connection with a wireless device. The base station may send an RRC message, to the wireless device, to transition the first wireless device from an RRC connected state to an RRC inactive state, the RRC message indicating an active time period in which the wireless device is reachable by paging. In an example, the base station may receive from an access and mobility management function (AMF), a context setup request message requesting a connection establishment with the wireless device. The context setup request message may comprise an indication that the MICO mode is allowed for the wireless device and the active time period. The base station may determine whether to apply the MICO mode based on the context setup request message. The base station may start a timer based on the active time period in response to sending the RRC message. The base station may receive first packet data associated with the wireless device, from a user plane function (UPF), before an expiration of the active time period. The base station may send paging messages to the wireless device based on the first packet data. The base station may receive second packet data associated with the wireless device, from the UPF, after the expiration of the active time period. The base station may not send paging messages to the wireless device based on the second packet data.

In this specification, a and an and similar phrases are to be interpreted as at least one and one or more. In this specification, the term may is to be interpreted as may, for example. In other words, the term may is indicative that the phrase following the term may is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. If A and B are sets and every element of A is also an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B={cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) may comprise one or more objects, and each of those objects may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J, then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages but does not have to be in each of the one or more messages.

Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an isolatable element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (i.e hardware with a biological element) or a combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. Additionally, it may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. Finally, it needs to be emphasized that the above mentioned technologies are often employed in combination to achieve the result of a functional module.

Example embodiments of the invention may be implemented using various physical and/or virtual network elements, software defined networking, virtual network functions.

The disclosure of this patent document incorporates material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, for the limited purposes required by law, but otherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the spirit and scope. In fact, after reading the above description, it will be apparent to one skilled in the relevant art(s) how to implement alternative embodiments. Thus, the present embodiments should not be limited by any of the above described exemplary embodiments. In particular, it should be noted that, for example purposes, the above explanation has focused on the example(s) using 5G AN. However, one skilled in the art will recognize that embodiments of the invention may also be implemented in a system comprising one or more legacy systems or LTE. The disclosed methods and systems may be implemented in wireless or wireline systems. The features of various embodiments presented in this invention may be combined. One or many features (method or system) of one embodiment may be implemented in other embodiments. A limited number of example combinations are shown to indicate to one skilled in the art the possibility of features that may be combined in various embodiments to create enhanced transmission and reception systems and methods.

In addition, it should be understood that any figures which highlight the functionality and advantages, are presented for example purposes. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable the U.S. Patent and Trademark Office and the public generally, and especially the scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. The Abstract of the Disclosure is not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include the express language means for or step for be interpreted under 35 U.S.C. 112. Claims that do not expressly include the phrase means for or step for are not to be interpreted under 35 U.S.C. 112. 

What is claimed is:
 1. A method comprising: receiving, by a wireless device from a base station, a radio resource control (RRC) message to transition the wireless device from an RRC connected state to an RRC inactive state, the RRC message indicating a time period in which the wireless device is reachable by paging; transitioning, by the wireless device and in response to the RRC message, from the RRC connected state to the RRC inactive state while remaining in a connection management (CM) connected state; monitoring, in the RRC inactive state, to receive a paging message during the active time period after the transitioning; and in response to an expiration of the time period: activating a mobile initiated communication only (MICO) mode; and stopping monitoring to receive the paging message.
 2. The method of claim 1, further comprising sending, by the wireless device to the base station, an RRC resume request message to establish an RRC connection for mobile originated data transmission during the time period.
 3. The method of claim 1, further comprising sending, by the wireless device to the base station, an RRC resume request message to respond to a paging message during the time period.
 4. The method of claim 1, wherein the wireless device stays in the RRC inactive state based on the activating the MICO mode.
 5. The method of claim 4, further comprising sending, by the wireless device to the base station, an RRC resume request message to establish an RRC connection for a mobile originated data transmission based on the activating the MICO mode.
 6. The method of claim 1, wherein the wireless device transitions to an RRC idle state based on the activating the MICO mode.
 7. The method of claim 6, further comprising sending, by the wireless device to the base station, an RRC setup request message to establish an RRC connection for a mobile originated data transmission based on the activating the MICO mode.
 8. The method of claim 1, further comprising sending, by the wireless device to an access and mobility management function (AMF) via the base station, a registration request message indicating that the wireless device prefers the MICO mode.
 9. The method of claim 1, wherein the RRC message comprises parameters for RRC suspension, wherein the parameters comprises at least one of: a radio network temporary identity (RNTI); a radio access network (RAN) paging cycle; a RAN notification area (RNA) indication; or a periodic RNA update time value.
 10. The method of claim 9, wherein the time period is smaller than the periodic RNA update time value.
 11. A wireless device, comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to: receive, from a base station, a radio resource control (RRC) message to transition the wireless device from an RRC connected state to an RRC inactive state, the RRC message indicating a time period in which the wireless device is reachable by paging; transition, in response to the RRC message, from the RRC connected state to the RRC inactive state while remaining in a connection management (CM) connected state; monitor, in the RRC inactive state, to receive a paging message during the time period after transitioning from the RRC connected state to the RRC inactive state in response to the RRC message; and in response to an expiration of the time period: activate a MICO mobile initiated communication only (MICO) mode; and stop monitoring to receive the paging message.
 12. The wireless device of claim 11, wherein the instructions further cause the wireless device to send to the base station an RRC resume request message to establish an RRC connection.
 13. The wireless device of claim 11, wherein the instructions further cause the wireless device to send to the base station an RRC resume request message to respond to a paging message during the time period.
 14. The wireless device of claim 11, wherein the wireless device stays in the RRC inactive state based on activation the MICO mode.
 15. The wireless device of claim 14, wherein the instructions further cause the wireless device to send to the base station an RRC resume request message to establish an RRC connection based on activation of the MICO mode.
 16. The wireless device of claim 11, wherein the instructions further cause the wireless device to transition to an RRC idle state based on activation of the MICO mode.
 17. The wireless device of claim 16, wherein the instructions further cause the wireless device to send to the base station an RRC setup request message to establish an RRC connection based on activation of the MICO mode.
 18. The wireless device of claim 11, wherein the instructions further cause the wireless device to send, to an AMF via the base station, a registration request message indicating that the wireless device prefers the MICO mode.
 19. The wireless device of claim 11, wherein the RRC message comprises a parameter for RRC suspension, wherein the parameter for the RRC suspension comprises an RNA update time value equal to or larger than the time period.
 20. A system comprising: a base station comprising: one or more first processors; and first memory storing instructions that, when executed by the one or more first processors, cause the base station to; determine to release a radio resource control (RRC) connection with a wireless device; send, to the wireless device, an RRC message to transition the wireless device from an RRC connected state to an RRC inactive state, the RRC message indicating a time period in which the wireless device is reachable by paging; and the wireless device comprising: one or more second processors; memory storing second instructions that, when executed by the one or more second processors, cause the wireless device to; receive, from the base station, the RRC message; transition, in response to the RRC message, from the RRC connected state to the RRC inactive state while remaining in a connection management (CM) connected state; monitor, in the RRC inactive state, to receive a paging message during the time period after transitioning from the RRC connected state to the RRC inactive state in response to the RRC message; and in response to an expiration of the time period: activate a mobile initiated communication only (MICO) MICO mode; and stop monitoring to receive the paging message. 